Having problems with your account or logging in?
A lot of changes are happening in the community right now. Some may affect you. READ MORE HERE

How does Silk Performer handle a "cache-control: no-cache" http header?

How does Silk Performer handle a "cache-control: no-cache" http header?

A server may send a "cache-control: no-cache" HTTP header to the browser to try to ensure it doesn't cache a document, and that consequently has to resend the request on navigating one page back.

However, the Silk Performer recorder must change this header to allow the recording of a meaningful script. Instead of sending "no-cache" the recorder sends the "private" header.  This is a little bit weaker and allows the browser to use its cache on hitting the back button.

Note: Not all browsers will implement this in the same way when the back button is used with cache-control. Opera (5) browser does not resend the request whereas a Netscape browser always resends the requests on pressing the back button.

If an application uses the "window.history.go(-1)" method to simulate hitting the back button and the "cache-control: no-cache" header is sent from the server the browser should resend the request for the url.  However, if the "cache-control: private" header is sent to the browser then the browser will use the url from its cache.

As a workaround to this issue you should allow the cached page to load, delete the url from the cache (INTERNET OPTIONS| GENERAL TAB | SETTINGS | VIEW FILES, taking care not to delete the cookies and manually reload it i.e. enter the url into the address field.

For further details on the Cache-control header please see


Some content on Community Tips & Information pages is not officially supported by Micro Focus. Please refer to our Terms of Use for more detail.
Top Contributors
Version history
Revision #:
1 of 1
Last update:
‎2013-02-15 19:00
Updated by:
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.