IIS 5 & IIS 6
File Cache not serving updated file.
Last post Apr 23, 2008 01:40 PM by horwitzd
Jan 30, 2008 04:02 PM|horwitzd|LINK
We have an internal web site containing just static .html pages. When we update the content, by ftp-ing the updated files and overwriting the current content, the previous content keeps displaying.
We have seen this behavior for our home page, which has a URL (internally accessible only) of http://proPhysician.phci.org/index.html. When it is accessed using that URL, IIS serves the old content. When accessed as http://proPhysician.phci.org, IIS serves
the updated content. (We have the default page set to index.html).
Restarting IIS clears the problem and displays the updated content for both URLs.
Does someone have any ideas on how to get IIS to use the updated content for http://proPhysician.phci.org/index.html without forcing a restart of IIS?
Daniel S. Horwitz (horwitzd)
ProHealth Care, Inc.
Feb 04, 2008 10:18 PM|steve schofield|LINK
Sounds like you have some type of proxy server, caching server or the content is cached in the browser. have you tried making sure it's not cached on your server? Try using WFETCH or Fiddler on a remote server after you update the file. See if the changes
Windows Server MVP - IIS
Log archival solution
Install, Configure, Forget
Apr 23, 2008 01:29 PM|markware62|LINK
Did you ever figure this out? We are experiencing this as well
Apr 23, 2008 01:40 PM|horwitzd|LINK
No, we haven't figured it out, but we have discovered some additional information.
There is a timeout for how long to keep an entry in the cache, ObjectCacheTTL. Its default value is 30 (seconds). We set it to 60 (seconds) with no effect. To disable the cache, set DisableMemoryCache to 1. This settings are described in
http://www.microsoft.com/technet, search for "Global IIS Caching Registry Entries (IIS 6.0)".
The really interesting thing is that the problem is intermittent, and seems to not happen in certain directories. Also, when the problem occurs, the new file replaces the old file in the cache after exactly 60 minutes. I've asked around amoung our network
engineers and no one knows of a 60 minute cache time or a 60 minute timeout.
This may also be related to specific machines. Our files are updated using ftp. When we tried to reproduce the cache issue on a test machine, we were unable to reproduce the problem.
Hope this helps,
Daniel S. Horwitz