firefox - Why does the expiration date of the request cache lie in the past? -


i working on caching pages , noticed in firebug:

cache expiration date lying in past

so says cache expired 45 years ago. bug or bad data?

i have page caching correctly

correct cache expiration date

i not understand why saying expires ... 1970. page won't cache @ on site, though i'm using boost module drupal.

if expires header set 0, browser interprets 1 january 1970, relates unix time aka posix time. because date lies in past, means request not cached.

the expires header defined within rfc 7234, includes paragraph related statement above:

a cache recipient must interpret invalid date formats, value "0", representing time in past (i.e., "already expired").


Comments

Popular posts from this blog

javascript - gulp-nodemon - nodejs restart after file change - Error: listen EADDRINUSE events.js:85 -

Fatal Python error: Py_Initialize: unable to load the file system codec. ImportError: No module named 'encodings' -

javascript - oscilloscope of speaker input stops rendering after a few seconds -