Mailing-List: contact bugs-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache HTTPD Bugs Notification List" <bugs@httpd.apache.org>
From: bugzilla@apache.org
To: bugs@httpd.apache.org
Subject: DO NOT REPLY [Bug 15866]  -
    cache MUST treat incomplete cached response as partial
Message-Id: <20050606154035.DEB1D1B0@ajax.apache.org>
Date: Mon,  6 Jun 2005 17:40:35 +0200 (CEST)

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=15866>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=15866


------- Additional Comments From coad@measurement-factory.com  2005-06-06 17:40 -------
Yes, adding code to invalidate cache entries when Content-Length
mismatches that actual length will remove this violation and may
improve cache robustness overall. IIRC, Squid does something like
that.

A "proper" (but much more difficult) fix is to support caching of
partial responses. Very few caches are capable of that. However,
the first step would still be the detection of a partial response,
just like in the simple solution above. Thus, that code will not
be wasted.


-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org