> I
> played with setting my dispatch handler as a PerlTransHandler, but
> mod_proxy seems
> to get in there first no matter how I setup the config file, so I got it
> in at the
> PerlPostReadRequestHandler. But for what it's worth, examining proxyreq
> value in
> later phases (access, response) i
On Feb 19, 2004, at 12:35 PM, Stas Bekman wrote:
*snip*
I have a PerlPostReadRequestHandler running on a proxy server (using
mod_proxy)
that wants to intercept/handle various requests directly while
proxying others
normally.
[...]
I'd like to just call '$r->proxyreq(0)' to disable mod_proxy for t
> I have a PerlPostReadRequestHandler running on a proxy server (using
> mod_proxy)
> that wants to intercept/handle various requests directly while proxying
> others
> normally. To achieve this I currently match against the
> '$r->unparsed_uri()' and
> actually clear PerlTransHandler ('$r->set_
John D.Lima wrote:
Hi,
[Apache 2.0.48/mod_perl 1.99_12, linux (debian) 2.4.x]
Anyone using the $val arg for Apache::RequestRec::proxyreq(), per
http://perl.apache.org/docs/2.0/api/Apache/RequestRec.html#C_proxyreq_ ?
synopsis:
$ret = $r->proxyreq($val);
* arg1: $r (Apache::RequestRec)
*
Hi,
[Apache 2.0.48/mod_perl 1.99_12, linux (debian) 2.4.x]
Anyone using the $val arg for Apache::RequestRec::proxyreq(), per
http://perl.apache.org/docs/2.0/api/Apache/RequestRec.html#C_proxyreq_ ?
synopsis:
$ret = $r->proxyreq($val);
* arg1: $r (Apache::RequestRec)
* arg2: $val (intege
