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=39274>. 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=39274 Summary: Reverse Proxy Mangles multipart/form-data content in POST Product: Apache httpd-2 Version: 2.0.55 Platform: Other OS/Version: FreeBSD Status: NEW Severity: critical Priority: P1 Component: mod_proxy AssignedTo: [email protected] ReportedBy: [EMAIL PROTECTED] We are using Apache 2.0.x as a reverse proxy/SSL handler in front of back-end Apache 1.3.x/mod_perl servers. After a recent multi-version upgrade of our front-end from 2.0.44 to 2.0.55, we found that some POST transactions were not working properly. We eventually came up with a testcase that caused problems consistently, and upon monitoring the traffic between the frontend and back-end server, discovered that the multipart/form-data content of the POST transaction was being mangled. Specifically, the beginning of that data disappeared, while the end portion of the data remained. This only seems to happen when the content-length reaches at least a certain size - we found it at a content-length of about 3525. At that content length, the problem is fully reproducable, while shorter content lengths do not appear to cause the problem to appear. Downgrading to 2.0.54 resolved this issue, so I believe this is a regression between those two versions. Several of the proxy items in the 2.0.55 changelog seem to relate to content-length handling, which makes them seem like likely candidates for causing this problem. We are using mod_proxy via mod_rewrite - the rewrite rule that's causing the proxying that exhibits this problem is: RewriteRule ^/(.*) http://127.0.0.1:8001/$1 [P] I assume that's not really relevant, but wanted to include it for completeness. I will attach two files after submitting this bug, the first is a capture of the sent request (thanks to FireFox' LiveHTTPHeaders extension, since the transaction takes place over SSL), and the second is the tcpdump output showing the communication between frontend and backend for that same request. Let me know if I can provide any further details to help track this down. -- 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]
