Pages do not expire as expected after you change Web site content

Article ID: 319384 - View products that this article applies to.
This article was previously published under Q319384
Expand all | Collapse all

SYMPTOMS

If you change content on a Web site, the changes do not appear as expected. Instead, Internet Information Services (IIS) 5.0 and later versions of IIS return the old content.

CAUSE

This can occur if HTTP compression is enabled on the Web server. Enabling HTTP compression introduces a new metabase key named HcCacheControlHeader. The default value of HcCacheControlHeader is set to max-age=86400 (that is, 86400 seconds). This means that the Web site stays in the cache of the browser for 24 hours.

RESOLUTION

  1. On your server, open a command prompt.
  2. Change to your X:\InetPub\AdminScripts folder, where X is the drive that you specified for your IIS documents.
  3. Run the following command:
    CSCRIPT.EXE ADSUTIL.VBS SET W3SVC/Filters/Compression/Parameters/HcCacheControlHeader "max-age=0"

    Note In IIS 7.0, the name of the configuration key is CacheControlHeader. If the IIS 6 Management Compatability role is installed, run the command in step 3 to modify its value. Otherwise, use the Appcmd.exe tool.
  4. Stop and restart the IISAdmin service.
  5. Restart the WWW service.

WORKAROUND

If the client refreshes the content (for example, by pressing the F5 key), the IIS cache is updated and shows the changed content.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

MORE INFORMATION

Setting the value of Response.Expires to 0 in the relevant ASP page does not resolve the issue.

Properties

Article ID: 319384 - Last Review: June 26, 2008 - Revision: 4.0
APPLIES TO
  • Microsoft Internet Information Services 7.0
  • Microsoft Internet Information Services 6.0
  • Microsoft Internet Information Services 5.0
Keywords: 
kbprb KB319384

Give Feedback