hi all,
i am using Apache::DB to debug my mod_perl handlers and altough the
debugger seems to be working fine it won't display the source code next
to the current line being debugged. for example:
DB10 r
scalar context return from CODE(0x8d7101c): - undef
hi all,
i am using Apache::DB to debug my mod_perl handlers and altough the
debugger seems to be working fine it won't display the source code next
to the current line being debugged. for example:
DB10 r
scalar context return from CODE(0x8d7101c): - undef
hi there,
someone asked a similar question a while ago and here the answer that i
gave them... i think it answers your question too.
START
apache uses a simple technique for determining the path_info. it starts
at your document root and looks for the directory you specified in your
hi,
apache uses a simple technique for determining the path_info. it starts
at your document root and looks for the directory you specified in your
URI. it continues to go deeper in the directory structure until it
encounters a directory(or file) that doesn't exist. when this happens
the the
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
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: