Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 354737 - www-servers/apache-2.2.x (including latest in ~amd64) contain a bug in mod_ssl which causes mod_proxy to fail on SSL proxying
Summary: www-servers/apache-2.2.x (including latest in ~amd64) contain a bug in mod_ss...
Status: RESOLVED DUPLICATE of bug 354297
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Server (show other bugs)
Hardware: All Linux
: High major (vote)
Assignee: Gentoo Linux bug wranglers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-02-13 14:35 UTC by Heiko Wundram
Modified: 2011-02-13 14:46 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Heiko Wundram 2011-02-13 14:35:03 UTC
The bug specified in

https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/589611

(or originally)

https://issues.apache.org/bugzilla/show_bug.cgi?id=45444

affects forwarding sessions using mod_ssl; they fail to work, because of an invalid memcpy, which should be a memmove. The corresponding errors that can be seen in the mod_proxy-processing apache webserver is:


[Sun Feb 13 13:26:02 2011] [warn] proxy: bad HTTP/1.1 header returned by /wp-login.php (POST)
[Sun Feb 13 13:26:06 2011] [warn] proxy: bad HTTP/1.1 header returned by /wp-login.php (POST)
[Sun Feb 13 13:26:09 2011] [warn] proxy: bad HTTP/1.1 header returned by /wp-login.php (POST)

(in this case, for forwarding to an internal WordPress installation). Applying the patch that is referenced in the Apache-Tracker bug solves the problem.

Reproducible: Always

Steps to Reproduce:
1. Install apache, configure a mod_proxy setup which forwards to an SSL-URL
2. Try to access the corresponding mod_proxy URL

Actual Results:  
Errors as specified above.

Expected Results:  
Working access.

I'm not sure why this error only appeared after upgrading to openssl-1.0.0d, but applying the patch that is referenced in the apache-tracker bug solves this. I'd say that the specified patch should be included in the gentoo apache-patch series.
Comment 1 Chí-Thanh Christopher Nguyễn gentoo-dev 2011-02-13 14:46:07 UTC

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