Why? Output Caching Automatically Disables Browser Caching in IIS 7.5

Question

In IIS 7.5, when I don't have Output Caching enabled, my php script successfully sets browser caching in the Cache-Control header:

Cache-Control: max-age=43200,public
Content-Type: text/html
Expires: Wed, 30 May 2012 22:15:18 GMT
Server: Microsoft-IIS/7.5
X-Powered-By: PHP/5.4.3
Date: Wed, 30 May 2012 10:15:18 GMT
Connection: close
Content-Length: 5105

However, if I enable Output Caching for .php files, I get the following header:

Cache-Control: no-cache,max-age=43200,public
Content-Type: text/html
Expires: Wed, 30 May 2012 22:25:34 GMT
Server: Microsoft-IIS/7.5
X-Powered-By: PHP/5.4.3
Date: Wed, 30 May 2012 10:25:34 GMT
Connection: close

(notice "no-cache" is added to the Cache-Control before my php script's work)

There is no way, I've found, to prevent "no-cache" from being added to the Cache-Control key, if Output caching is enabled for a file type. I've tried to do it in the web.config file:

        <customHeaders>
            <remove name="X-Powered-By" />
    <remove name="Cache-Control" />
            <add name="Cache-Control" value="public" />
        </customHeaders>

That doesn't work. Why must this be so mutually exclusive? I'd like to have both Output Caching and Browser Caching enabled.

score 9 · Accepted Answer · answered May 30 '12 at 22:03

9

Unfortunately the IIS Manager interface does not allow you to use all features that are supported by the output caching module. One of these features is to set the cache location that indirectly controls the cache-control header. You have to manually edit your web.config to change it. The syntax is like:

<caching>
    <profiles>
        <add extension=".php" ..... location="Any" />
    </profiles>
</caching>

The <add /> tag will have more option depending on how you want your caching to work. The important part is to add the location="..." attribute. The following values are supported and they control the cache-control header as follows:

Any or Downstream = public

ServerAndClient or Client = private

None or Server or empty = no-cache

As the location attribute is absent by default, IIS will by default send a Cache-Control: no-cache header when output caching is enabled. More information about output caching and the supported features can also be found at: Response caching in IIS7

answered May 30 '12 at 22:03

Marco Miltenburg

6,123
1
29
29

1

You're awesome. Adding the location attribute solved my problem. I can't thank you enough. Many thanks! – Lonnie Best May 30 '12 at 22:43
Do you have any suggestions for adding a dynamic Expires http header? See here: http://stackoverflow.com/questions/10825497/iis-7-5-how-do-you-add-a-dynamic-http-expires-header – Lonnie Best May 30 '12 at 23:09
Answered that question individually. – Marco Miltenburg May 31 '12 at 12:05
Many years later, you saved my sanity and the rest of my schedule... Thanks! – Rolf Jan 27 '21 at 13:30

Why? Output Caching Automatically Disables Browser Caching in IIS 7.5

1 Answers1