During replay when using SilkPerformer 2007 patch 3 you may find that a page is taken from the SilkPerformer document cache even though when the page was first initially requested by the SilkPerformer Replay Engine the server response header specified that the document had expired as was therefore un-cacheable. The HTTP headers below provide an example of such Expires HTTP headers: Expires: -1 Or Expires: Fri, 30 Oct 1998 14:19:41 GMT To prevent the SilkPerformer Replay Engine from caching un-cacheable documents please install Hotfix 11 for SilkPerformer 2007. The Hotfix can be acquired by contacting Support.
↧