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=36883>. 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=36883 ------- Additional Comments From [EMAIL PROTECTED] 2005-10-06 22:22 ------- (In reply to comment #2) > I can reproduce the problem with 5.5.12 (and httpd 2.0.8) as well, so since > from the lack of response no one in tomcat-dev appears to care about problems > with 5.0.x, I'm modifying the record to show that it effects the current > development branch, too. It seems that the problem is that mod_proxy_ajp isn't playing nice with mod_ssl (so that this is really a Httpd bug). Even when the connection isn't HTTPS, mod_proxy_ajp is sending (empty) SSL attributes like cipher, client- cert, session-id. This causes Tomcat to believe that the request was recieved on HTTPS, so it redirects accordingly. Below is a dump of the Request message that Tomcat recieves from Httpd: FINE: 12 34 00 6b 02 02 00 08 48 54 54 50 2f 31 2e 31 | .4.k....HTTP/1.1 FINE: 00 00 0c 2f 74 6f 6d 63 61 74 2d 64 6f 63 73 00 | .../tomcat-docs. FINE: 00 09 31 32 37 2e 30 2e 30 2e 31 00 ff ff 00 07 | ..127.0.0.1.??.. FINE: 68 6f 75 73 74 6f 6e 00 22 b8 00 00 02 a0 0b 00 | houston."?...?.. FINE: 0c 68 6f 75 73 74 6f 6e 3a 38 38 38 38 00 00 0c | .houston:8888... FINE: 4d 61 78 2d 46 6f 72 77 61 72 64 73 00 00 02 31 | Max-Forwards...1 FINE: 30 00 07 00 00 00 08 00 00 00 09 00 00 00 ff | 0.............? -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]