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 Invalid response headers Summary: Invalid response headers Product: Apache httpd-2.0 Version: 2.0.36 Platform: All OS/Version: All Status: NEW Severity: Critical Priority: Other Component: mod_proxy AssignedTo: [email protected] ReportedBy: [EMAIL PROTECTED] Build & Platform: Apache/2.0.36 Sun Solaris 5.8 Within the 1.3.x implementation of mod_proxy, response headers appear to be handled differently in 2.0 when a CRLF does not separate the header from the message body. Apache 1.3.x handles this gracefully by continuing to process the request, however, 2.0 sends back a 502 error when a CRLF separator is not present. The following response header worked in 1.3, but now breaks in 2.0: HTTP/1.1 200 OK Server: Microsoft-IIS/4.0 Date: Sun, 18 Aug 2002 06:18:39 GMT Content-type: text/html <HTML> <-- NO CRLF SEPARATING HEADER FROM BODY! ... </HTML> Will 2.0 not incorporate this functionality as well? Thanks, Brian --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
