Http Scripting Hints
Static Resources
Requests for static resources like images, style sheets, scripts should typically be disabled since they are handled by the browser cache. When importing a recording all requests which were covered by the browser cache during recording are disabled. You can disable or enable all http messages that the EEM editor considers as static by using the function Script -> Hide Static Messages. Technically, the editor checks the HTTP response header Content-Type of the recording against a fixed list of mime types (e.g. images, Javascript, css) that are considered as static.
Note, however, that this simple heuristics built into the EEM Editor might not catch all messages that are actually static or candidates for caching. So it might make sense to review the remaining active requests manually in addition.
Common URLs that Should be Disabled / Deleted
The following URLs are typically not part of the business transaction and should be disabled or removed from the script:
https://urs.microsoft.com/urs.asmx
(Microsoft phishing filter)
http://www.google-analytics.com/
(Google Analytics)
Runtime Error in Editor when Displaying Html Pages
The editor uses the Internet Explorer rendering engine to display http responses. In many cases, the individual http responses are incomplete - they depend on the responses from other requests, like style sheets and javascripts. As a consequence, the rendering looks "damaged" and you may also get Javascript runtime errors and you are asked to launch a debugger:
To get rid of this error:
- Launch Internet Explorer
- Go to Tools --> Internet Options, tab Advanced
- Check the item Disable Script Debugging (Other):
