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