On Wed, Sep 19, 2012 at 3:46 PM, Mario A. del Riego <delriego@xxxxxxxxxxx> wrote: > Supid, > > I have the same behavior, it's a bug well documented at [1]. > > If you know the redirection, you can do it in the front-end. > In my particular case, i fixed it with mod_security. I have wrote a > little in my blog [0] (in spanish) about this. > > > [0] http://blog.makam.org/2012/09/01/bug-en-mod_proxy/ > [1] https://issues.apache.org/bugzilla/show_bug.cgi?id=51489 > I don't believe this is a bug. In the configuration he says ProxyPassReverse / http://fooremote.com/ What this actually means is: Every time one of the special headers has a value that starts with the value "http://fooremote.com/";, replace that value with the canonical name of this vhost, as per canonicalisation rules. Now, his backend generates a header with this value "http://fooremote.com:80/wibble";. This does not match the configured value, and so therefore is not rewritten. You are not limited to one ProxyPassReverse statement, so the OP can do this: ProxyPass / http://fooremote.com/ ProxyPassReverse / http://fooremote.com/ ProxyPassReverse / http://fooremote.com:80/ Alternatively, OP could fix his backend so that it doesn't produce silly output like that in headers. Cheers Tom --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|