| Subject: | Excessive persistence causes crashes |
| Date: | Wed, 17 Oct 2012 15:34:38 -0700 |
| To: | bug-CGI-Application-FastCGI [...] rt.cpan.org |
| From: | rt.cpan.org [...] ch.pkts.ca |
Hello!
I've written a test application that uses CGI::Application::FastCGI,
and found that if I called
$self->redirect('?rm=login');
then I'd have to have this code in cgiapp_prerun:
${$self}{'__PRERUN_MODE'}='';
or else no pages would be generated until the fastcgi instance was
restarted.
My program uses the following modules:
use base qw(CGI::Application::FastCGI);
use CGI::Application::Plugin::DBH qw(dbh_config dbh);# For database
interaction
use CGI::Application::Plugin::Forward; # For passing control
use CGI::Application::Plugin::ErrorPage 'error'; # For errors
use CGI::Application::Plugin::Session; # For session support with
cookies
use CGI::Application::Plugin::Redirect; # For redirecting pages
use Crypt::PasswdMD5; # For verifying passwords
use POSIX qw(strftime);
use Data::Dumper;
use URI::Escape;
To decide whether any particular behaviour is wrong, just remember that
the cgi application should run the same with or without FastCGI. I
don't know enough about the internals of CGI::Application and friends
to be certain, but shouldn't $self be mostly regenerated for every
query?
Thanks for a great framework!
CH