DO NOT REPLY [Bug 8677] - mod_proxy ALWAYS nukes Content-Length
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=8677. 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=8677 Bug 8677 depends on bug 18757, which changed state. Bug 18757 Summary: Content-Length is removed from replies to HEAD requests http://issues.apache.org/bugzilla/show_bug.cgi?id=18757 What|Old Value |New Value Status|NEW |RESOLVED Resolution||FIXED -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 8677] - mod_proxy ALWAYS nukes Content-Length
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=8677. 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=8677 mod_proxy ALWAYS nukes Content-Length [EMAIL PROTECTED] changed: What|Removed |Added Status|RESOLVED|CLOSED - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 8677] - mod_proxy ALWAYS nukes Content-Length
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=8677. 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=8677 mod_proxy ALWAYS nukes Content-Length [EMAIL PROTECTED] changed: What|Removed |Added BugsThisDependsOn||18757 Status|REOPENED|RESOLVED Resolution||DUPLICATE --- Additional Comments From [EMAIL PROTECTED] 2003-11-26 14:03 --- mod_proxy no longer nukes Content-Length header but a related CONTENT_LENGTH filter bug, #18757, breaks responses to HEAD requests and breaks Windows Update clients. #18757 contains a patch to fix the problem but apparently no-one has had time to commit the patch. *** This bug has been marked as a duplicate of 18757 *** - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 8677] - mod_proxy ALWAYS nukes Content-Length
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=8677. 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=8677 mod_proxy ALWAYS nukes Content-Length [EMAIL PROTECTED] changed: What|Removed |Added CC||[EMAIL PROTECTED] Status|CLOSED |REOPENED Resolution|FIXED | --- Additional Comments From [EMAIL PROTECTED] 2003-10-01 16:22 --- I do still have problems with Windows Update using apache 2.0.47. Cu - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 8677] - mod_proxy ALWAYS nukes Content-Length
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=8677. 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=8677 mod_proxy ALWAYS nukes Content-Length [EMAIL PROTECTED] changed: What|Removed |Added Status|RESOLVED|CLOSED - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 8677] - mod_proxy ALWAYS nukes Content-Length
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=8677. 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=8677 mod_proxy ALWAYS nukes Content-Length [EMAIL PROTECTED] changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2003-01-21 15:43 --- Patch to fix this has been commited to v2.0.45-dev and v2.1.0-dev. If this does not fix this problem, please reopen this bug. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 8677] - mod_proxy ALWAYS nukes Content-Length
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=8677. 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=8677 mod_proxy ALWAYS nukes Content-Length --- Additional Comments From [EMAIL PROTECTED] 2002-07-05 09:23 --- Oops, ignore the last comment, I managed to post it to the wrong bug. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 8677] - mod_proxy ALWAYS nukes Content-Length and Transfer-Encoding if body sent
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=8677. 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=8677 mod_proxy ALWAYS nukes Content-Length and Transfer-Encoding if body sent [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |ASSIGNED --- Additional Comments From [EMAIL PROTECTED] 2002-05-05 18:00 --- Stripping the Transfer-Encoding header is required by RFC2616, as it is a hop by hop header, so this behaviour is correct. As to stripping the Content-Length, I understand that the Content-Length filter is responsible for putting in this header, although if the content length is already there, I see no point in stripping it. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 8677] - mod_proxy ALWAYS nukes Content-Length and Transfer-Encoding if body sent
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=8677. 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=8677 mod_proxy ALWAYS nukes Content-Length and Transfer-Encoding if body sent [EMAIL PROTECTED] changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution||INVALID --- Additional Comments From [EMAIL PROTECTED] 2002-05-05 18:45 --- Answer from the dev list: Justin Erenkrantz wrote: Nah, this allows us flexibility in optimizing the data sent to our client. If we can send chunked-encoding, I believe that is a better than using C-L. I believe that the RFC allows us to do these sorts of optimizations. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 8677] - mod_proxy ALWAYS nukes Content-Length
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=8677. 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=8677 mod_proxy ALWAYS nukes Content-Length [EMAIL PROTECTED] changed: What|Removed |Added Severity|Normal |Enhancement Status|RESOLVED|REOPENED Resolution|INVALID | Summary|mod_proxy ALWAYS nukes |mod_proxy ALWAYS nukes |Content-Length and Transfer-|Content-Length |Encoding if body sent | --- Additional Comments From [EMAIL PROTECTED] 2002-05-05 19:47 --- I think I'll reopen this, at least until someone can convince me that this is really how things should be. It certainly seems like it is allowed, and it shouldn't actually break any clients, but it does not seem at all optimal. For HTTP/1.0 clients it verges on very bad behvior. I'll also downgrade to Enhancement and remove the encoding reference. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
