You are viewing a plain text version of this content. The canonical link for it is here.
Posted to bugs@httpd.apache.org by bu...@apache.org on 2002/12/30 19:11:42 UTC
DO NOT REPLY [Bug 11800] -
Handling Invalid proxied response headers
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=11800>.
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=11800
Handling Invalid proxied response headers
wrowe@apache.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Keywords| |FAQ
Resolution| |FIXED
Summary|Invalid response headers |Handling Invalid proxied
| |response headers
------- Additional Comments From wrowe@apache.org 2002-12-30 18:11 -------
The next release will include the ProxyBadHeader directive; providing you
the option to handle bad headers with IsError, Ignore, or StartBody
semantics. The IsError case works as 2.0 does today, the Ignore case will
still look for the two successive cr/lf pairs but discarding the invalid
header lines (as 1.3 really does today), while StartBody will behave as
you are hoping, starting the response body with the first bad header line.
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org