register_cleanup() in PerlInitHandler harmful?

I have a dumb question about register_cleanup() in Apache 1.x and mod_perl 1.27. yesterday I released Apache::Profiler to dump slow URI to log file, which seems to be useful. However it uses register_cleanup() in PerlInitHandler and it seems to break whole things because of, I guess,

[mp2 module rfc] Apache::Filter::HTTPHeadersManip

As I was writing for Chris the test that manipulates HTTP headers and seeing that it's not trivial for the end users (due to the http_in core httpd filter's implementation), I've realized that the functionality of manipulating HTTP headers can be abstracted, letting the end user do very little

Re: [mp2 module rfc] Apache::Filter::HTTPHeadersManip

Ged Haywood wrote: Hi Stas, On Tue, 7 Oct 2003, Stas Bekman wrote: came up with Apache::Filter::HTTPHeadersManip which you can try [snip] If you have comments regarding the naming http://www.m-w.com/cgi-bin/dictionary?manipulate I wonder if Manip would be better replaced by Alter. If the

RE: [QUESTION] Relating a request to a response

I would be quite interested in testing it once it's complete. --- Regards, Chris Pringle UK PSG Hewlett-Packard, Bristol Tel: +44 117 31 29664 Mob: +44 7793 681024 -Original Message- From: Stas Bekman [mailto:[EMAIL PROTECTED] Sent: 07 October 2003 17:27 To: Pringle, Chris

Re: Mod_perl with NLDBM issue

Chris M wrote: I am trying to get a new configuration going. When I start 2.0.47 I get: # /etc/rc.d/init.d/httpd start Starting httpd: Syntax error on line 1110 of /etc/httpd/conf/httpd.conf: Perl directive missing closing '' [FAILED] It should be Perl in mp2. ^

simple two server (front end - back end) setup help

Hi there everyone, I'm setting up a simple two server setup with mod_perl. I've tested static documents, and they work fine. The ones I have a rewrite rule for are served by the front end, and the ones not in the rule by the backend. The problem comes when I run perl scripts (via

Re: Mod_perl with NLDBM issue

Chris M wrote: On 10/8/03 10:14 AM, Stas Bekman [EMAIL PROTECTED] wrote: Chris M wrote: I am trying to get a new configuration going. When I start 2.0.47 I get: # /etc/rc.d/init.d/httpd start Starting httpd: Syntax error on line 1110 of /etc/httpd/conf/httpd.conf: Perl directive missing

Re: Mod_perl with NLDBM issue

Chris M wrote: I am trying to get a new configuration going. When I start 2.0.47 I get: # /etc/rc.d/init.d/httpd start Starting httpd: Syntax error on line 1110 of /etc/httpd/conf/httpd.conf: Perl directive missing closing '' [FAILED] Line 1110 is the Perl line below: PerlModule

Re: $ENV{PATH} and PerlTaintCheck On

James Tolley wrote: Hi, Date::Manip is used from a module that's used from a handler. Perl dies when I try to ParseDate or Unixdate a date - saying that $ENV{PATH} is insecure. I've tried to set $ENV{PATH} = '...' in a BEGIN block, and I've tried setting it from PerlSetEnv PATH ... How can I

Re: $ENV{PATH} and PerlTaintCheck On

Hi Stas, On Wed, 8 Oct 2003, Stas Bekman wrote: Ged Haywood wrote: On Wed, 8 Oct 2003, James Tolley wrote: How can I untaint $ENV{PATH}?? You have to do it in those (appropriate) places where the data appear, in every request. Use a substitution command to convert characters

Re: Mod_perl with NLDBM issue

On 10/8/03 12:45 PM, Stas Bekman [EMAIL PROTECTED] wrote: Chris M wrote: The opening is Perl , but the clsoing is /Perl. It wan't the space in the opening tag, because in httpd-2.0 the parser requires an argument in all containers (with a leading space), so opening Foo is invalid, but it's

mod_perl 2: $r-get_server_port returns wrong value

Is it possible that the value returned by $r-get_server_port could be affected by the format or content of the client request? I've got a test case where when i hit the same URL from two different clients I get different values from $r-get_server_port. This doesn't make sense to me, because I

RE: Using class wide variables under mod_perl is safe?

Hi, You're making this much harder than it needs to be. For one thing, this is the wrong place to use inheritance, and for another, globals are okay if used intelligently. A database handle is a bad example. You actually should use Apache::DBI for that, since it will make sure the handle

RE: Using class wide variables under mod_perl is safe?

Hi, Thanks for the detailed information that's great. A couple of things though. A database handle is a bad example. You actually should use Apache::DBI for that, since it will make sure the handle hasn't timed out and deal with rolling back any pending transactions if your code dies. So,

cvs commit: modperl-2.0/xs/tables/current/ModPerl FunctionTable.pm

geoff 2003/10/08 06:28:14 Modified:lib/ModPerl Code.pm t/response/TestApache conftree.pm xs/tables/current/ModPerl FunctionTable.pm Removed: t/hooks default_port.t t/hooks/TestHooks default_port.pm Log: undo

cvs commit: modperl-2.0 Changes

geoff 2003/10/08 06:29:18 Modified:.Changes Log: Revision ChangesPath 1.231 +0 -2 modperl-2.0/Changes Index: Changes === RCS file: /home/cvs/modperl-2.0/Changes,v retrieving