perl-modperl mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Torsten Krah <tk...@fachschaft.imn.htwk-leipzig.de>
Subject Re: mod_perl - Intercepting an external Redirect
Date Fri, 21 Sep 2007 07:37:52 GMT
Am Donnerstag, 20. September 2007 schrieben Sie:
> On 9/19/07, Torsten Krah <tkrah@fachschaft.imn.htwk-leipzig.de> wrote:
> > Now i configured the "otherhost" to do a permanent redirect when
> > /time/blog is requested.
> > If i request this uri, the redirect is done like configured there - my
> > filter does not get called.
>
> It's possible that mod_proxy doesn't cooperate with filters, but I
> thought it did.  You might try turning on some mod_rewrite logging to
> get a better view of what's happening.  You could also do the proxy
> request yourself from perl, although it's less efficient than
> mod_proxy.
>
> - Perrin

Hm i did found a case where its not working like i want.
All works fine, but if the proxy request, which is done after my filter issued 
the internal_redirect, fails - because of dns error or something else which 
does result in 5xx Code, the error output of mod_proxy is printed to the 
client inclusive the "internal" url, which i want to hide.

So my question is - is there any way to get a filter which may prevent this 
situation "afterwards", a request output filter is ignored in failure case - 
may i need a connection handler?

Or should i do the proxy request in my first outputfilter with perl tools 
instead of doing the internal_redirect and let mod_proxy do the job?

thx for help and hints.

Torsten

Mime
View raw message