Does your handler use Apache::Registry or Apache::PerlRun by any chance?
I did find this code snippet from the ap_add_cgi_vars() within,
the Apache core...
if (r->path_info && r->path_info[0]) {
/*
* To get PATH_TRANSLATED, treat PATH_INFO as a URI path.
* Need to r
Hi,
I followed Lyle's advice and moved my module down to the
PerlFixupHandler phase and also added the extra logging info.
However I still get, as predicted, one initial request for the correct
URI and another subrequest for a URI which corresponds to the value I
set the path_info to. If I do
Hello all,
I have the following question on which I would appreciate any insight.
I have written a failry simple multiplexing PerlTransHandler. Its task
is to check the uri and if it matches a certain string then push an
associated PerlHandler onto the stack. An example can make it clearer:
L