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]
