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=42492>. 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=42492 Summary: mod_proxy_ajp with SSL front end: data corruption of large POST request Product: Apache httpd-2 Version: 2.2.4 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P2 Component: mod_proxy AssignedTo: [email protected] ReportedBy: [EMAIL PROTECTED] When accessing Tomcat through mod_proxy_ajp: <IfModule mod_proxy.c> ProxyPass /webapp ajp://localhost:8009/webapp ProxyPassReverse /webapp ajp://localhost:8009/webapp </IfModule> and the initial request is received by Apache over HTTPS, large POST data bodies are often not received by Tomcat. The POST request in question had about 56kB of data. The problem is intermittent, in that the POST data does, on occasion, arrive properly. Even if the POST data does not arrive (Tomcat reports null values for POST data parameters) the request's Content-Length header is still received properly, but not the data itself. This is easily shown by accessing a JSP page that displays both the header and the POST request parameters. The problem was experienced running both Apache 2.2.0 and Apache 2.2.4 against Tomcat 5.5.20, both on SuSE 10.1 and on Mac OS X 10.4.8. Please note: - It is Apache that is accessed over HTTPS, not Tomcat. - Problem does not occur when accessing Apache through non-secure HTTP. - Problem does not occur when accessing Tomcat directly over HTTP (port 8080), bypassing Apache. - Problem DOES occur when using mod_jk instead of mod_proxy_ajp, and again, only over HTTPS. - Problem does not occur when proxying into the Tomcat HTTP connector: <IfModule mod_proxy.c> ProxyPass /webapp http://localhost:8080/webapp ProxyPassReverse /webapp http://localhost:8080/webapp </IfModule> The notes above lead me to believe the issue is with mod_proxy_ajp, but then, I'm not an expert. Some digging around in bugzilla found an eerily similar bug in mod_proxy_http, bug number 37415 (http:// issues.apache.org/bugzilla/show_bug.cgi?id=37145), that was fixed in httpd-2.0.56. Which might explain why the HTTP proxy connection to Tomcat port 8080 is working, but the AJP proxy is not. -- 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]
