DO NOT REPLY [Bug 22951] - ProxyErrorOverride On sends wrong Content-length header after a 302 response

[bu...@apache.org]

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=22951>.
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=22951





------- Additional Comments From sebastiaan@kantoor.nederhost.nl  2006-01-09 19:44 -------
We just ran into this bug on an Apache 2.0.55 combination of proxy and backend server. Our backend 
server does not provide any content on a 302, resulting in the proxy server returning a 302 with 
content but content-length set to 0. 

I do not see what this has to do with cookie support. To me, sending a content-length header that 
indicates a wrong content length is clearly broken, regardless of whether a 3xx error should be handled 
by ProxyErrorOverride. This broken response confuses some browsers while using keepalive, such as 
the antique but still widely used Firefox 1.0.7.

The invalid response also occurs if an ErrorDocument is defined. Specifying an ErrorDocument of 0 
bytes results in the ErrorDocument being ignored (which is probably the sane way to handle that). Being 
no workaround available, could this problem be fixed so that 302 at least works? Our system 
administrator is not too wild about custom patches, so we've turned ProxyErrorOverride off for now.

-- 
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