DO NOT REPLY [Bug 8677] - mod_proxy ALWAYS nukes Content-Length

[bu...@apache.org]

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

siegfried.delwiche@sbs.be changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|Enhancement                 |Major



------- Additional Comments From siegfried.delwiche@sbs.be  2002-08-26 14:50 -------
I suggest to raise level to an higher level since this is really blocking (at 
least the content-length header).
A typical application not working anymore is the windows update tool

As far as I understand the protocol, it mentions 
14.13
The Content-Length entity-header field indicates the size of the entity-body, 
in decimal number of OCTETs, sent to the recipient or, in the case of the HEAD 
method, the size of the entity-body that would have been sent had the request 
been a GET. 

Windows update makes a HEAD request on the cab file that contains the updater 
program and gets in trouble since it does not receive a content length.

Hope this will be fixed soon.

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