What is the best way to combine CGI::Session and CGI::Application
It was recommended that I use the cgiapp_init, which I am attempting to do.
But do I set the
$self-header_props inside the cgiapp_init sub then do nothing else. Or
should I follow the CGI::Session docs and initialize a new
Hi
But do I set the
$self-header_props inside the cgiapp_init sub then do nothing else. Or
should I follow the CGI::Session docs and initialize a new instance of
CGI.pm and print the header directly from the cgiapp_init sub?
If you are using CGI::Application, then you don't have to create
Sorry to be a little slow about this, the code below does appear to working
now. But I am concerned that it might not be the correct way of doing it.
I seem to have a little disfunctional code at the end; last two lines. Is
that right?
sub cgiapp_init {
my $self = shift;
my $q
. Ruzmetov [EMAIL PROTECTED]
To: Zachary Buckholz [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Thursday, May 16, 2002 3:10 PM
Subject: Re: [cgiapp] CGI::App and CGI::Session
my $new_cookie = $self-header_props(-name=COOKIE,
-value=$session-id);
$self-header_props(-cookie=$new_cookie
use constant COOKIE = saint;
But I should propably be using .securitysaint.com
No, COOKIE constant was just a name of the cookie to be sent.
It has nothing to do with the domain name.
Alternative for using constant is to give the name
for the cookie on the fly:
$new_cookie =
