Detail the contextual information specific to the issue; i.e. Product, Version, Agent, System, etc.
Describe the problem, from the user perspective
Many customers may have questions about the browser cache :
Clearly list the Steps to resolve the issue
When a test runs in the Synthetic Classic Portal, the browser cache is cleared after each test run.
To create a test that uses the browser cache, first consider how the cache is used:
Generally, browsers create a cache of the web pages you visit to load the page faster for subsequent visits to the page. But whether a browser uses the cache depends on the user's actions and the cache control HTTP headers.
To create a test that uses the cache or refreshes the target page, there are three possibilities:
In Internet Explorer, Firefox, and Chrome, the page is cached when you first visit a web page. Then:
This table summarizes browsers behaviors:
* The browser will read the cache, then only send requests to those objects that don't t have an Expire header or that have an Expire header but have expired.
The attached scripts Re-Visit.gsl,F5-Refresh.gsl and CtrlF5-Refresh.gsl demonstrate how the local cache works and how to create a script with a local cache. Since the Browser Agent agent cleans the cache after each test run, the script needs to load the same page in Step 1 to generate the cache. That means you cannot create a one-step test to see the result for re-visit, refresh or force refresh.
The Repeat Visitor feature in the Windows Recorder is a solution for Re-visit. This feature is only available for the IE Agent. If you enable Repeat Visitor, it runs the same test twice in the same browser window, using the cached page for the second run; only the response time data for the second run is stored in the Synthetic Classic database.