we have the following in our web.config: <staticFile expirationTime="12:0:0" />
if i clear my cache and access www.pension.dk i get all static content and the status on the responce is 200 OK if i access the page again before the cache expires my browser does not request the cached items, so far so good.
but if i try to access the page after the cache has expired my browser sends an If-Modified-Since and the server responds with a 304 Not Modified and that responce does not contain a new Expires header with a date 12 hours in the future. and the Cache-Control header is just set to provate, no max-age set.
this means that every time i access an page on pension.dk after cache has expired the browser sends an If-Modified-Since request and gets a 304 Not Modified responce for every static resource.
what i would like to have happen is that the 304 Not Modified responce header includes a Expires header with a date 12 hours in the future, this way the browser will opdate the cache with the new expires date and not request the item again until it expires again.
this behaivor is the same for all browsers.
this is the If-Modified-Since request and 304 Not Modified responce:
hello
we have the following in our web.config: <staticFile expirationTime="12:0:0" />
if i clear my cache and access www.pension.dk i get all static content and the status on the responce is 200 OK
if i access the page again before the cache expires my browser does not request the cached items, so far so good.
but if i try to access the page after the cache has expired my browser sends an If-Modified-Since and the server responds with a 304 Not Modified and that responce does not contain a new Expires header with a date 12 hours in the future. and the Cache-Control header is just set to provate, no max-age set.
this means that every time i access an page on pension.dk after cache has expired the browser sends an If-Modified-Since request and gets a 304 Not Modified responce for every static resource.
what i would like to have happen is that the 304 Not Modified responce header includes a Expires header with a date 12 hours in the future, this way the browser will opdate the cache with the new expires date and not request the item again until it expires again.
this behaivor is the same for all browsers.
this is the If-Modified-Since request and 304 Not Modified responce:
private
0
text/html
Tue, 23 Oct 2012 11:24:53 GMT
"1CB138FFA259850"
Microsoft-IIS/7.5
2.0.50727
ASP.NET
text/css,*/*;q=0.1
gzip, deflate
da,en-us;q=0.7,en;q=0.3
keep-alive
__utma=1.1788595876.1338273972.1350103214.1350462067.28; __utmz=1.1338542693.3.2.utmcsr=google|utmccn
=(organic)|utmcmd=organic|utmctr=(not%20provided); pension.dk=section=ompensiondanmark
www.pension.dk
Thu, 24 Jun 2010 11:25:40 GMT
"1CB138FFA259850"
http://www.pension.dk/
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20100101 Firefox/15.0.1
private
15254
text/css
Tue, 23 Oct 2012 11:24:53 GMT
"1CB138FFA259850"
Wed, 17 Oct 2012 20:24:25 GMT
Thu, 24 Jun 2010 11:25:40 GMT
Microsoft-IIS/7.5
2.0.50727
ASP.NET