I was going off of the CAP-Session documentation: "... The recommended place to call session_config is in the cgiapp_init stage of CGI::Application. If this method is called after the session object has already been accessed, then it will die with an error message. ..."
My app appears to work with session_config under cgiapp_prerun. I will give that a try. Thanks! -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of [email protected] Sent: Sunday, June 19, 2011 2:01 AM To: CGI Application Subject: Re: [cgiapp] Sessions leaking with FastCGI "Victor Bruno" <[email protected]> writes: > I am going to try moving my session_config call to prerun from init, since > init does not get called on every page request with FastCGI. I'd guess that's your bug and solution right there. And you'd have that same problem in any persistent environment. - dave ##### CGI::Application community mailing list ################ ## ## ## To unsubscribe, or change your message delivery options, ## ## visit: http://www.erlbaum.net/mailman/listinfo/cgiapp ## ## ## ## Web archive: http://www.erlbaum.net/pipermail/cgiapp/ ## ## Wiki: http://cgiapp.erlbaum.net/ ## ## ## ################################################################ ##### CGI::Application community mailing list ################ ## ## ## To unsubscribe, or change your message delivery options, ## ## visit: http://www.erlbaum.net/mailman/listinfo/cgiapp ## ## ## ## Web archive: http://www.erlbaum.net/pipermail/cgiapp/ ## ## Wiki: http://cgiapp.erlbaum.net/ ## ## ## ################################################################
