Server: Apache/1.3.37 (Unix) mod_perl/1.29
During an active development cycle, with many changes and updates,
perl cgi pages are getting "stuck" in the mod_perl.
The symptom is, for example a syntax error which has been fixed
sporadically reappears, but goes away again on refresh.
When it gets r
Hello.
Running Apache 2.2.12, mod_perl 2.0.4, perl 5.10.0, and CGI.pm 3.29.
I've noticed what seems to be a case of Taint mode being ignored with
respect to CGI params when running under mod_perl.
The following:
#!/usr/bin/perl -T
use strict;
use warnings;
$E
On Tue, May 25, 2010 at 10:22 AM, Jonas Bull wrote:
> During an active development cycle, with many changes and updates,
> perl cgi pages are getting "stuck" in the mod_perl.
How are you running this code? Is it through ModPerl::Registry? Are
there modules involved?
- Perrin
[ please keep it on the mailing list ]
On Tue, May 25, 2010 at 2:25 PM, Jonas Bull wrote:
> httpd.conf has the following:
> SetHandler perl-script
> PerlSendHeader On
> PerlHandler Apache::Registry
> Options ExecCGI
Okay,
Apologies for the direct reply. Apparently the list isn't its own reply-to...
#Code_has_been_changed__but_it_seems_the_script_is_running_the_old_code
Describes pretty much what is happening, except the code changes in
question are definitively NOT in modules, which is why I find it
strange. In
On Tue, May 25, 2010 at 4:01 PM, Jonas Bull wrote:
> In the logs, I see notification of the changes to the script
> - sometimes. Most of the time, actually. But occasionally the
> process fails to catch the changes, which is annoying, but not as
> troubling as the case where the script seems to
Last I heard, taint mode in mod_perl didn't always work. See:
http://marc.info/?l=apache-modperl&m=119749949626698&w=2
That was a while back, maybe it's been fixed by now.
-Scott.
On Tue, May 25, 2010 at 10:26 AM, Nik Ogura wrote:
> Hello.
>
> Running Apache 2.2.12, mod_perl 2.0.4, per
It isn't always variable related... But I can see where maybe upload
new version=>refresh page=>get a stale process could be happening.
In this situation the httpd does not recognize the -X option.
I guess we'll have to wait longer.
A server update is in the works, though.
Jonas Bull
601-324-0
