Good suggestions, but both should be unnecessary. CGI::Session uses a
finalizer to ensure the session is closed and all the builtin session stores
update on close. No expires means the cookie lives for the duration of the
browser session.
Your source suggested you may be sending a malformed HTTP response. Inspect
the request and response in Firebug to see: look for the Set-Cookie header
in the response and the Cookie header in subsequent requests.
jeremy
···
On 2/24/07, ara.t.howard@noaa.gov <ara.t.howard@noaa.gov> wrote:
On Sun, 25 Feb 2007, Dsa Dang wrote:
>> you need to make sure you flush and close it.
>
> I've added sess.close at the end but it still doesn't work
>
Good suggestions, but both should be unnecessary. CGI::Session uses a
finalizer to ensure the session is closed and all the builtin session stores
update on close. No expires means the cookie lives for the duration of the
browser session.
--
be kind whenever possible... it is always possible.
- the dalai lama
So.. my friend have found what was wrong. It's all about session id.
Here it must be send manually. I'll leave the source here as it may be
deleted from the server soon (first old source, then correct and
working).