On a FYI level the following works:
#!/usr/bin/perl
use strict;
use Apache2::Const();# defines OK
use Apache2::Log();# defines warn
use Apache2::RequestUtil();# defines push_handlers
my $r = shift;
$r-push_handlers(PerlCleanupHandler = \cleanup);
print Content-type:
So this works almost perfectly... Almost because:
#!/usr/bin/perl
use strict;
use Apache2::Const();# defines OK
use Apache2::Log();# defines warn
use Apache2::RequestUtil();# defines push_handlers
my $r = shift;
$r-push_handlers(PerlCleanupHandler = \cleanup );
Fellow mod_perlers,
Here's a weird one for you. I'm testing Bricolage on mod_perl 2, getting it
ready for release, and noticed that some sort of redirect is happening when I
don't expect it.
To whit, I have this configuration:
NameVirtualHost *:80
VirtualHost *:80
DocumentRoot
On Tue, Jan 26, 2010 at 2:58 PM, David E. Wheeler da...@kineticode.com wrote:
Fellow mod_perlers,
Here's a weird one for you. I'm testing Bricolage on mod_perl 2, getting it
ready for release, and noticed that some sort of redirect is happening when I
don't expect it.
To whit, I have this
On Jan 26, 2010, at 3:18 PM, Fred Moyer wrote:
I don't know if this could be an issue, but if I were to write this
config snippet, I would create a root Location / block, and put the
transhandler outside that (with the other location based directives
inside).
The transhandler isn't used in
Caveat Lector:
Long Cleanups done inline on the Apache children can cause problems.
If you get a situation where the CleanUp takes to long OR you get
enough traffic to the page(s) which engage the CleanUp then you will
encounter a tipping point, and soon after your website will be almost
I have banged my head against this one for a few days but can't get
perl 5.10.1, 2.2.14, mod_perl 2.0.5-dev working on Snow Leopard.
There are some other similar problems you will find for Snow Leopard
through Google, with ruby, python, etc., but none of those have led to
a fix for this problem.
On our site we create a new CGI::Session object at the beginning of
the request, so that it can be used anywhere in the web code.
However, sessions are rarely written to, so at the end of the request
I'd like to avoid actually writing out a new session to backing store
unless a param
This never got a response. Which surprises me, since I think it is a
legitimate and nasty bug.
So is the silence because
1) people don't think it's really a bug
2) people glazed over while reading the description
3) ??
Thanks :)
Jon
On Jan 8, 2010, at 6:15 AM, Jonathan Swartz wrote:
(A
Sorry if this is naive, but has anyone gotten this combo to work? Upgraded
to Apache 2.2.14, now crash on almost every request, then next httpd picks
up the request and actually displays the page...
I've got massive core dumps all ending in malloc/free, truss shows last
operation was close()
On Tue, Jan 26, 2010 at 5:20 PM, Jonathan Swartz swa...@pobox.com wrote:
This never got a response. Which surprises me, since I think it is a
legitimate and nasty bug.
So is the silence because
1) people don't think it's really a bug
2) people glazed over while reading the description
3) ??
The warning from William T. made me think to ask:
Does your site have KeepAlive On in httpd.conf?
(If not I can't think of anything to suggest...)
If so, try adding this as part of the redirect:
use Apache2::Connection();
use Apache2::RequestRec();
...
my $c = $r-connection();
What OS are you running? What is the output of 'perl -V'?
On Tue, Jan 26, 2010 at 6:19 PM, Pas Argenio pas.arge...@gmail.com wrote:
Sorry if this is naive, but has anyone gotten this combo to work? Upgraded
to Apache 2.2.14, now crash on almost every request, then next httpd picks
up the
13 matches
Mail list logo
