Brian Akins wrote:
Paul Querna wrote:
Related issue:
http://issues.apache.org/bugzilla/show_bug.cgi?id=15866
I don't think its breaking the RFC to not-cache partial pages.
Yep. That's my issue:
This one doesn't have an easy solution. The problem is that mod_proxy
currently
has no way to tell mod_cache if a response terminated abnormally. We
could add
some code in mod_cache, to make sure Content-Length matches that
actual length,
and invalidate the cache at that point.
I would really like to use the "stock" 2.2 proxy modules, but I cannot
with this "bug."
As a quick fix, could we not have proxy set r->status =
HTTP_BAD_GATEWAY or something and re-check in the cache before
finalizing the store?
Yes, and then remove the problem content and header file.
-Paul
