httpd-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Petter Olofsson" <>
Subject [users@httpd] Url decoding problem with the ProxyPassReverse
Date Tue, 21 Oct 2008 18:20:53 GMT
I'm running Apache 1.3 and Resin 3.1.6 on Ubuntu.

The problem is that slashed urls forwarded to the resin server are
decoded twice, first in apache and then in resin.

Requests are going to Apache and are forwarded to the Resin server
with the ProxyPassReverse command.

The rewrite is looking like this:

RewriteCond             %{REQUEST_URI}          (.*)
RewriteRule             ^(/query(/.*)?)$ [L,P]
ProxyPassReverse        /query         

This works just fine when we are using a normal url, for instance:
In resin we can see that parameters foo is bar and search is H + H
after decoding.

When we use a slashed url, http://localhost/query/foo/bar/search/H%20%2B%20H
%2B is decoded into a '+'-sign in apache and is forwarded as such to
resin. (%20 is not decoded.)

Resin decodes the + into a space character and gives us the "search=H
 H" instead of "search=H + H" which was what we wanted.

We have tried to do an ugly quick fix  and url-encode the parameters
with +-signs in them twice, with the hope of apache decoding %252B
into just %2B. That did not work since apache is not keen on decoding

I've seen a similar question in archive
and the solution for Linde was to use an Base64 encoding, but that
isn't what I'm doing, or can one encode the url again before
forwarding the request to resin?

Thankful for any help that I can get

The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:> for more info.
To unsubscribe, e-mail:
   "   from the digest:
For additional commands, e-mail:

View raw message