Bug 38141 - mod_proxy crrupt data when forward a https PUT request.
Summary: mod_proxy crrupt data when forward a https PUT request.
Status: RESOLVED DUPLICATE of bug 37145
Alias: None
Product: Apache httpd-2
Classification: Unclassified
Component: mod_proxy (show other bugs)
Version: 2.0.55
Hardware: Other other
: P2 normal (vote)
Target Milestone: ---
Assignee: Apache HTTPD Bugs Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-01-05 20:44 UTC by Shien Xie
Modified: 2006-01-05 12:10 UTC (History)
0 users


Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Shien Xie 2006-01-05 20:44:50 UTC 
The bug is seen under Apache 2.0.55 + openssl 0.9.8a configuration.
Apache 2.0.54 + openssl 0.9.7g configuration works fine.

We have a web server consists two Apache instances.
The frontend has https enabled and use mod_proxy to forward requests to backend 
Apache instance, particularlly, we use mod_dav in backend server and want to 
upload files to the web server.

When we try to upload files, we found that mod_proxy forwards corrupted data to 
the backend Apache instance as long as the data trunk is greater than a certain 
size. In our case, it is ok to forward 4K but 50K is not. 

-- If disable SSL in the frontend, mod_proxy works fine.
-- If the file does not go to backend(mod_proxy), (enable mod_dav in frontend 
instance), the file will not be corrupted.

It seems that mod_proxy can not handle https request correctly.
Comment 1 Ruediger Pluem 2006-01-05 21:10:42 UTC 
Sounds to me like bug #37145. Please try the patch attached to this bug.

*** This bug has been marked as a duplicate of 37145 ***