DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7808>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7808 HTTP GET causes Squid 2.4 never to serve cached objects ------- Additional Comments From [EMAIL PROTECTED] 2002-05-10 11:11 ------- I belive that RFC 2616 gives no help here. However, this quote from < http://www.squid-cache.org/bugs/show_bug.cgi?id=337 > may give support for your suggestion, rwaldhof (which also was implied by my bug report): HTTP does not define the semantics of a request entity for GET. A 0 bytes long request entity is still a request entity. The correct thing is to not include a Content-Length header in GET requests. In fact, most Squid versions completely reject GET requests at all having a Content-length header. It is only very resently we have begun accepting such requests, and only Content-length: 0. (the acceptance of -1 is a bug or unexpected sideeffect, don't rely on it). Incidentally your problem with MISS on such requests is fixed in Squid-2.5. The way we deal with request entities is rewritten there and as a sideeffect GET .. Content-length: 0 requests now generate cache hits where applicable. No plans on doing anything about it in Squid-2.4. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
