So what do you think? Should this be Apache::current_callback or
ModPerl::Util::current_callback? If Apache::current_callback should it be
still live in ModPerl::Util?
I tend to move to ModPerl::Util::current_callback, since current_callback is
not really in Apache API.
Stas Bekman wrote:
[EM
I'm not sure what to do about the untaint() function. In mp1 it's
Apache->untaint and in mp2 it's ModPerl::Util::untaint. This function cheats
and turns the tainted variables untainted, without a proper laundering, but it
does that fast. We use it internally in things like Registry scripts, to s
Stas Bekman wrote:
[EMAIL PROTECTED] wrote:
stas2003/03/02 19:50:55
Modified:.STATUS
Log:
log the issue with ${^TAINT} returning -1 with blead-perl-ithreads
Can somebody please test whether you get
t/TEST modperl/taint
fail on winXX with ithreads blead perl? (it won'
Stas Bekman wrote:
Ask Bjoern Hansen wrote:
On Mon, 17 Feb 2003, Stas Bekman wrote:
We'd be happy to host such a repository over at cvs.perl.org.
(Easier/lower overhead to get people commit access there than at
cvs.apache.org).
+1, Thanks Ask!
Ask, so how do we take it from here? I now have fix
Doug MacEachern wrote:
On Sun, 9 Mar 2003, Stas Bekman wrote:
I wish Doug would follow up and explain why was it dumped from the 2.0 API in
first place.
you'll need to ask [EMAIL PROTECTED] for details, but the jist is that
filters handle sending headers at the proper time. not sure if the
Matt Sergeant wrote:
On Mon, 10 Mar 2003, Stas Bekman wrote:
Nick Tonkin wrote:
Stas:
Cgensym> in the docs throws an error with my 5.8.0 perldoc:
[EMAIL PROTECTED] ~/tmp>perldoc porting.pod
porting.pod:200: Unknown escape E<>
porting.pod:205: Unknown escape E<>
Thanks Nick, I've fixed it (shou
On Sun, 9 Mar 2003, Stas Bekman wrote:
> I wish Doug would follow up and explain why was it dumped from the 2.0 API in
> first place.
you'll need to ask [EMAIL PROTECTED] for details, but the jist is that
filters handle sending headers at the proper time. not sure if the reason
matters much,
