HTTP headers
2001-07-25 15:27:03+00 by
Dan Lyke
2 comments
Just because I'm too lazy to deeply delve into the appropriate RFC right now: Does anyone have a good idea what HTTP headers I should be sending to better expire the archives pages? So far as I can tell, the HTML and CGI headers I'm getting back from each are identical, yet it seems like cache checking is happening properly for the static HTML pages and not for the CGI served pages (note to self: answer might be in RFC3143).
[ related topics:
Web development
]
comments in ascending chronological order (reverse):
#Comment made: 2002-02-21 05:32:21+00 by:
dws
This is going to sound like overkill, but a lot of testing on a serious web application suggests sending all of
- A post-dated
Expires:
header
Pragma: no-cache
Cache-control: no-cache
The latter two deal with HTTP/1.0 and HTTP/1.1 compliant proxy servers, respectively.
#Comment made: 2002-02-21 05:32:23+00 by:
Dan Lyke
I don't want to constantly blow the cache, which is why I'm attempting to send a reasonable "Last-Modified" header (even for "HEAD" requests). I guess I need to investigate an "Expires" header half an hour or so into the future, and possibly try to expire the cache when you post to that same URL (so that message postings show up immediately).