Bug 233254 - mod_proxy not handling percent chars in URLs correctly
mod_proxy not handling percent chars in URLs correctly
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: httpd (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Joe Orton
Depends On:
  Show dependency treegraph
Reported: 2007-03-21 05:40 EDT by Jason Haar
Modified: 2007-11-16 20:14 EST (History)
0 users

See Also:
Fixed In Version: RHSA-2007-0747
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-11-15 10:06:21 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Apache Bugzilla 15207 None None None Never
Red Hat Product Errata RHSA-2007:0747 normal SHIPPED_LIVE Moderate: httpd security, bug fix, and enhancement update 2007-11-15 10:06:14 EST

  None (edit)
Description Jason Haar 2007-03-21 05:40:29 EDT
Description of problem:

Hi there

We are using httpd as a reverse proxy, and have been hit by the bug referenced
within Apache's bugtracker as


Supposedly it was fixed in 2.0.55 back in 2005?

Basically if you are using Apache as a RP, it "double-unescapes"
percent-encodings and ends up with an invalid URL

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. set up RP section via ProxyPass/ProxyPassReverse e.g

ProxyPass /test http://other.server/test/

2. download "rp.server/test/hel%20l%20o.txt - works (i.e. backend server 
3. download rp.srver/test/hel%20l%25o.txt - RP gives 400 error instead of
 passing back to backend server

Actual results:

Expected results:

Additional info:
Comment 1 Joe Orton 2007-05-16 09:54:32 EDT
Thanks for the report.
Comment 8 errata-xmlrpc 2007-11-15 10:06:21 EST
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.


Note You need to log in before you can comment on or make changes to this bug.