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 that indicates that the cached copy is
still up to date, mod_cache serves the contents of the cache to the
client with a 200 code.

This wouldn't surprise me.  There's currently a bug open for the
opposite case, returning a 304 to an unconditional request (45341).

I believe this violates a SHOULD in 14.25 of RFC 2616, which isn't as
strong as a MUST, but certainly would indicate it's worthwhile to try to
fix it.

I'd suggest opening a bug report
(http://httpd.apache.org/bug_report.html), including all the details
from your original message, so this doesn't fall through the cracks
before someone gets to look at it in more depth.

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.

Cheers,
Nicholas Sherlock

Reply via email to