On 6/8/05, Axel-Stéphane SMORGRAV <Axel-Stephane.SMORGRAV@xxxxxxxxxxxxxx> wrote: > 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?? I haven't tried it, but I don't believe this is possible. I believe that ProxyPassReverse simply looks at the Location: header coming back, and if it matches the ProxyPassReverse argument, it rewrites it. It does not compare to the path on the original request. Joshua. --------------------------------------------------------------------- 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
|