Home/ Questions/Q 4237196
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-21T02:44:29+00:00

Background A customer is running our web app. over HTTPS and are running into

  • 0

Background

A customer is running our web app. over HTTPS and are running into the (fairly well know) IE8 “file cannot be written to cache” error when they try to view a PDF/Excel/word file because the response contains the HTTP Cache-Control:no-cache directive. The thing is, it is not our app (or its config) that is adding this directive.

After a bit of investigating I discovered that the IIS7 page output caching feature can also add this header, for example 

<caching enabled="false" enableKernelCache="false">
    <profiles>
        <add extension=".htm" policy="CacheUntilChange" kernelCachePolicy="CacheUntilChange" />
    </profiles> 
</caching>

will have the effect of adding Cache-Control:no-cache, private to response headers.

My Question

But the surprising (IMO) thing is that even when you supposedly disable the feature (see in my config snippet above that enabled="false"), the response headers are still being sent with Cache-Control:no-cache, private.

Am I being stupid to be surprised by this (I guess I probably am)?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    You’re not alone: http://forums.iis.net/t/1152306.aspx

    We also had the same problem. I haven’t found any documentation about this “feature” so I’m assuming it is a bug.

    We decided to just remove the caching tag and use only the clientCache tag instead.

    • 0