I have set up a very long expiry on some files in my .htaccess (this is OK as I change the actual filename whenever its content changes).<FilesMatch min_\d+-\d+-\d+-\d+-\d+-\d+\.css$|min_\d+-\d+-\d+-\d+-\d+-\d+\.js$>Header set Cache-Control max-age=31536000, public</FilesMatch>Looking at the output of Firebug, the cache-control is getting passed through, but I notice that the 'Expires' in the response is set to 25th May (14 days in the future rather than 1 year as it aught to be). Does anyone have any ideas what is going on? Request HeadersAccept          text/css,*/*;q=0.1Accept-Encoding gzip, deflateAccept-Language en-US,en;q=0.5Connection      keep-aliveHost            redacted.co.ukReferer         http://redacted.co.uk/hh/main_minimised/User-Agent      Mozilla/5.0 (Windows NT 6.1; WOW64; rv:20.0) Gecko/20100101 Firefox/20.0Response HeadersAccept-Ranges       noneCache-Control       max-age=31536000, publicConnection          Keep-AliveContent-Encoding    gzipContent-Length      5576Content-Type        text/cssDate                Sat, 11 May 2013 22:46:47 GMTExpires             Sat, 25 May 2013 22:46:47 GMTKeep-Alive          timeout=5, max=99Last-Modified       Sat, 11 May 2013 17:12:31 GMTServer              ApacheVary                Accept-Encoding
Expiry date in response header contradicts the cache-control setting
cache control