Interesting read.
http://blogs.perl.org/users/josh_ben_jore/2010/07/the-mod-perl-debugger-youve-always-wanted.html
Notice that PerlSetEnv is allowed in scope DIR:
http://perl.apache.org/docs/2.0/user/config/config.html#mod_perl_Directives_Argument_Types_and_Allowed_Location
Try moving the PerlSetEnv line to inside the LocationMatch directive.
Although the above documentation indicates PerlSetVar is also of
Greetings mod_perl list!
I'm upgrading old debian servers to Ubuntu 10.04 and we have to upgrade
from apache 1.x and mod_perl to apache2 and mod_perl2.x This requires
rewriting configfiles and I'm running into the following problem:
I've got (sort of) the following apache configuration:
PerlSe
Hi Tobias,
your whole scenario depends on the possibility to reliably
cancel a running query on the database.
If your database and client (software) is able to do so,
which has to be tested, the cancel button could send
another ajax request with an identifier of the initial
query which then would
Hello,
I'm using
> apache 2.2.3
> mod_perl 2.0.2
> mod_apreq2 2.08
on a linux box.
In my enviroment a user can submit a query to a database. This request
is handled as an Ajax-request. If he forget to add some search parameters
this query can run a long time. So I add a "Cancel"-But
