Graham Leggett wrote:
Nicholas Sherlock wrote:
But couldn't it just send a 304 Not Modified code instead? At the moment
it ends up wasting large amounts of bandwidth on my website in the case
where you press refresh on an unmodified object in Firefox, which sends
these request headers:
I kept
Nicholas Sherlock wrote:
If you make a conditional request for a cached document, but the
document is expired in the cache, mod_cache currently passes on the
conditional request to the backend. If the backend responds with a 304
Not Modified response that indicates that the cached copy is
Hi everyone,
If you make a conditional request for a cached document, but the
document is expired in the cache, mod_cache currently passes on the
conditional request to the backend. If the backend responds with a 304
Not Modified response that indicates that the cached copy is still up
to
Nicholas Sherlock n.sherl...@gmail.com writes:
If you make a conditional request for a cached document, but the
document is expired in the cache, mod_cache currently passes on the
conditional request to the backend. If the backend responds with a
304 Not Modified response that indicates that
Dan Poirier wrote:
Nicholas Sherlock n.sherl...@gmail.com writes:
If you make a conditional request for a cached document, but the
document is expired in the cache, mod_cache currently passes on the
conditional request to the backend. If the backend responds with a
304 Not Modified response
Nicholas Sherlock wrote:
Thanks, I wasn't certain if the behaviour I wanted was HTTP-correct, but
it seems that it is (and anyway it'll save me on bandwidth costs, so I
really want to fix it). I'll go add it now.
This is now bug report #47580
