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=10052>. 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=10052 mod_proxy inserts a blank new line int headers when used in conjunction with mod_rewrite and mod_jk Summary: mod_proxy inserts a blank new line int headers when used in conjunction with mod_rewrite and mod_jk Product: Apache httpd-1.3 Version: HEAD Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: Other Component: mod_proxy AssignedTo: bugs@httpd.apache.org ReportedBy: [EMAIL PROTECTED] Given the following setup: <VirtualHost somehost> ServerName thisserver RewriteEngine On RewriteRule ^/gbuch$ http://someotherserver/guestbook/11/$gbuch/ [P] RewriteRule ^/gbuch/(.*) http://someotherserver/guestbook/11/$gbuch/$1 [P] </VirtualHost> <VirtualHost somehost> ServerName someotherserver JkMount /guestbook/* tomcat JkMount /guestbook tomcat </VirtualHost> (whereas tomcat is a working mod_jk setup) When I do a lynx -mime_header http://www.kaicity-festival.de/gbuch | head I get --- snip --- HTTP/1.1 200 Date: Thu, 20 Jun 2002 09:19:04 GMT Server: Apache/1.3.26 (Unix) mod_jk/1.1.0 mod_gzip/1.3.19.1a PHP/4.1.1 mod_perl/1.24_01 mod_ssl/2.8.9 OpenSSL/0.9.6 Content-Type: text/html; charset=iso-8859-1 X-Cache: MISS from thisserver Connection: close <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> --- snap --- Note the empty line between 'HTTP/1.1 200' and 'Date: ' This obviously confuses serveral browsers. When I use the proxy/* files from the 1.3.19 version of httpd I get: --- snip --- HTTP/1.0 200 Date: Thu, 20 Jun 2002 09:32:16 GMT Server: Apache/1.3.26 (Unix) mod_jk/1.1.0 mod_gzip/1.3.19.1a PHP/4.1.1 mod_perl/1.24_01 mod_ssl/2.8.9 OpenSSL/0.9.6 Content-Type: text/html; charset=iso-8859-1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> --- snap --- which of course works fine. So I think there is some kind of bug in mod_proxy. I was not able to reproduce it by proxying to a page that was not mod_jk/Tomcat 3.2.x generated. Best regards, Carsten --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]