We're in a similar situation. I've found two ways of doing this.
1. Use $ENV{'UNIQUE_ID'} (set my mod_unique_id?)
This seems to be a different value for every request. So I can create 2
global variables, $lastId and %savedData. If $lastId != $ENV{'UNIQUE_ID'}
then I know I'm in a new request a
Also, PerlHandler was replaced with PerlResponseHandler in 2.0.
PerlResponseHandler ModPerl::Registry
It's kind of tough learning mod_perl right now, because all the books give
1.0 examples, and 2.0 seems to have a lot of small differences. The docs
at perl.apache.org are a good reference. H
-8<-- Start Bug Report 8<--
1. Problem Description:
-
I'm trying to run some ModPerl::Registry and some mod_cgi scripts on
the same server. The problem is that sometimes the mod_cgi scripts
get no input for POST requests (STDIN is closed
Hi,
I mailed a bug report with this same subject a few days ago. I'm just
curious, does this sound like an unusual problem with my all of my builds,
or is this kind of problem with STDIN common when serving mod_cgi and
ModPerl::Registry scripts from the same apache?
I found an old post with a s
> > sub strip_end_data_segment {
> > -${ +shift->{CODE} } =~ s/__(END|DATA)__(.*)//s;
> > +${ +shift->{CODE} } =~ s/^__(END|DATA)__(.*)//ms;
> > }
> Sorry for the random, and probably naive question. What does the + in
> front of the shift do?
> --
> Regards,
> Iain
Check out "perldoc
