Axel-Stéphane SMORGRAV wrote: > Given the following reverse proxy configuration; > > <Location /first/> > ProxyPass http://appserver/ > ProxyPassReverse http://appserver/ > </Location> > > <Location /last/> > ProxyPass http://appserver/ > ProxyPassReverse http://appserver/ > </Location> > > whenever http://appserver/ (the backend server) returns a redirection (302), I want the Location header to be rewritten and prefixed with either /first/ or /last/ depending on the URL that the reverse proxy was invoked with. > > If I request http://reverse-proxy/last/path, and the backend server responds with a redirect to http://appserver/newpath, the client should receive a redirect to http://reverse-proxy/last/newpath. I thought this was the way it was supposed to work. > > However, instead the ProxyPassReverse in the first Location section applies, and I end up being redirected to http://reverse-proxy/first/newpath. > > Is this a bug, a feature, or is it just plain impossible to implement ProxyPassReverse the way I expected it to work?? It looks like http://marc.theaimsgroup.com/?l=apache-httpd-dev&m=110726027118798&w=2 Now I'm trying desparately to remember whether I got around to committing the fix for that one. -- Nick Kew --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|