-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello Patrick,
Patrick Coleman schrieb:
> I have a Tomcat app running on port 8080
>
> I can get to it through
>
> http://www.ourcompany.com:8080
>
> it goes to a login page and the URL displays
>
> http://www.ourcompany.com:8080/login
>
> I woul
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello Nick,
Nick Kew schrieb:
>> Why does mod_proxy behave this way? Is there a way to change the
>> behaviour? Do workarounds exist?
>
> http://issues.apache.org/bugzilla/show_bug.cgi?id=41798
>
> Stay tuned. I've been fixing quite a lot of mod_pr
ling list for this
problem [1] but the feedback is very sparse. Some people live with the problem,
some have built workarounds. It would be very helpful to have some solution to
it.
Best regards,
Robert Jaeschke
[1] e.g.
http://mail-archives.apache.org/mod_mbox/httpd-dev/200703.mbox/[EMAIL PR
Hello Pid,
Pid schrieb:
[...]
>>>between browser and mod_proxy:
>>>
>>>http://www.company.com/item-01-A1263%7E23334%2Cz831%7E238.asp
>>>
>>>between mod_proxy and back-end server:
>>>
>>>http://www.company.com/item-01-A1263%7E23334,z831%7E238.asp
>>>
>>>As you can see, mod_proxy is decoding
Hello Jeff,
Jeff Ambrosino schrieb:
> We have a mod_proxy (2.0.54) front-end proxying to a back-end MS IIS
> server. One type of URL that we use is causing problems because
> mod_proxy is decoding an encoded comma in the URL as it proxies the
> request to the back-end (we determined this with a p
Hello,
I'm using Apache (2.0.59) and mod_proxy as reverse proxy and want the
remote server pass URLs like
http://foo.com/bar/black%26white
Unfortunately, when using mod_proxy with ProxyPass and ProxyPassReverse,
this URL is rewritten to
http://foo.com/bar/black&white
which is bad (since on the
