I am running 5.7 build 644 of QA Load... I am having trouble starting or recording web applications in IE 6 SP3.
Here is an example.. I have QA Load configured to open the IE. The session used was WWW. while attempting to record.
If I enter an external URL such as www.yahoo.com for example ...no problem records fine.
I enter the url for my application and I get the page
Access Denied (policy_denied)
Your system policy has denied access to the requested URL.
For assistance, contact IT Support Center.
The capture displays the following:
WWW: 1 - Reply: 302 Found
WWW: 2 - Request: GET http://www.wsearch
WWW: 2 - Reply: 403 Forbidden
I know the application is up and running and I have no issues cause I can open up and navigate the web pages fine without QALoad.
I have also tried changing the record option to direct connection and bringing up the application on my own and nothing is recorded at all.
Has anyone encountered something like this? Any suggestions on how to address?
No authentication is required.
I don't think this is single sign on issue....
I have a script I recorded several months back under version 5.5 of qaload that I was able to record against. This same URL/Application now is giving me trouble...
Not sure if the new version of QA Load is the issue or if the companies tightened internet security is comming into play.
These are internal apps now ..BUT intended to be external once pushed to production.
I am not really going to wsearch.com..it looks like this is a redirect that happens...only while recording.
The odd part: I CAN record any external sites such as yahoo, compuware, microsft etc...it is all the local apps no login required I can't get into..
I did try 2 things since I last posted maybe this may shed some light.
I replaced the name of the server in the url with an ip address and that seemed to work partially...
I say that it worked partially beacuse it appears the functionality is there but some of the dynamic images are not loading. They are represneted as a blank (ie as if file not found found on the server)
My concern with this action is that it will not represent a true performance since loading pictures is part of displaying the web page.
My next action was to include a line in the hosts file to see if this would resolve the issue...it did not ...I am not a network or www person so just shooting in the dark..
Hope the extra information can help shed some light ...
Any other suggestions would be appreciated.
Follow up for anyone else who experiences same/similar issue:
In our environment in IE under Lan settings/Proxy Settings in the exceptions field are a list of all addresses that should not go through the proxy server.
Since this was a new application it was not stated in this field or fit any other wild-carded list of values previously listed. I added the server which is used in the url as part of the addresses wild-carded before recording in workbench. ie *newServer*
Then I recorded the application normally as stated previously and the error was not encountered.