What's the difference between the following three .htaccess rules and when to use each, is there any special use cases that prefers one over the other?:
Header set Cache-Control "max-age=290304000"
Header set Expires "Thu, 15 Apr 2020 20:00:00 GMT"
ExpiresDefault "access plus 10 years"
The first rule adds a max-age entry to Cache-Control. The browser has to refetch the document after the time in seconds given here.
The second and the third rules create expires headers. The browser has to refetch the document at the date given here. And the server has to do some calculations.
Note that the second rule forces a refresh for all browsers and all resources at the same time, while the third and the last rule invalidate the browser cache depending on the request time. You will see the difference if you have a site with much traffic: You will probably get a dramatic peak at 15 Apr 2020. :)
As a rule of thumb: Use max-age. It is very good supported and you don’t have the chance to create an invalid date. Additionally, it’s shorter.
Further reading:
Caching Tutorial for Web Authors and Webmasters – Required reading for every web developer.
Opera MAMA: HTTP Headers – Some interesting statistics, especially the full Expires frequency table is funny:
10 URLs authoritatively stated they are expired (and probably mummified) by using an expiry of "01 jan 0001".
Header is a directive of mod_headers that allows to modify HTTP header fields. In this case Header set effectively sets the mentioned header fields Cache-Control and Expires, so an already existing header field will be overwritten.
The first directive sets the header field Cache-Control with the value max-age=290304000, that describes the freshness lifetime to be 290304000 seconds relative to the response time.
In contrast to that, the second directive sets the header field Expires with the value Thu, 15 Apr 2020 20:00:00 GMT that describes the freshness lifetime with an absolute time value.
Both Cache-Control’s max-age value and Expires expiration time stamp can be transformed to the other:
The max-age directive takes priority over Expires, so if max-age is present in a response, the calculation is simply:
freshness_lifetime = max_age_valueOtherwise, if Expires is present in the response, the calculation is:
freshness_lifetime = expires_value - date_value
But if both are present, Cache-Control’s max-age is preferred over Expires:
If a response includes both an Expires header and a max-age directive, the max-age directive overrides the Expires header, even if the Expires header is more restrictive. This rule allows an origin server to provide, for a given response, a longer expiration time to an HTTP/1.1 (or later) cache than to an HTTP/1.0 cache. This might be useful if certain HTTP/1.0 caches improperly calculate ages or expiration times, perhaps due to desynchronized clocks.
In opposite to setting these HTTP caching control header fields manually, mod_expires ExpiresDefault directive allows an easy setup for HTTP caching. The freshness lifetime can either be described with an absolute value or with a relative value, either relative to the response time (i.e. access/now) or relative to the modification time of the requested file (i.e. modification). It uses both Cache-Control and Expires.
In this case the third directive sets the default freshness lifetime to be 10 years from the time of response on.
I would use mod_expires for HTTP cache control instead of doing it manually with Header. It is far more convenient, allows both relative and absolute freshness times and uses both Cache-Control and Expires.