Re: [cgiapp] C:A:Session Question

[Cees Hek <suppressed>]

Quoting Jason Purdy <suppressed>:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> I'm trying to understand the Session.pm module/plug-in and the
> documentation isn't helping me understand (that serves as a reflection
> on me, unfortunately -- not the docs ;)).

Hi Jason,

doc patches are always welcome ;)

> Anyway, my code (which I copied from the docs with minor tweaks) seems
> to be sending a new cookie every time instead of checking to see if the
> cookie exists.  Is there an option or something I'm missing so it
> doesn't re-issue another session?  Does the session object look for the
> session name based on the config change I made?  My /tmp subdir will
> fill up pretty quickly if I issue new cookies/sessions per request.

You are changing the name of the cookie, but not telling the CGI::Session module
about that change.  I guess the C::A::Session module could be more graceful in
handling this by checking to see if the -name parameter to the cookie has been
changed.  Currently it does not do that check.

All you need to do is tell CGI::Session what your cookie name is and things
should start working for you.

CGI::Session->name("FBM_Account");

And make sure that this is called before you make any call to $self->session,
since that is when the cookie header is set.  It probably makes sense to call
this just before your call to $self->session_config, in cgiapp_init.

Cheers,

Cees

---------------------------------------------------------------------
Web Archive:  http://www.mail-archive.com/suppressed/
              http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2
To unsubscribe, e-mail: suppressed
For additional commands, e-mail: suppressed