I just posted RC2 on http://bas.scheffers.net/aolserver/
This adds the keyword "never" to the possible values of expires.
Using this instead of a date a long time into the future will make it
possible to change the underlying code to not have a Y2033 problem
when cookie specs finalize.
I also updated the documentation of this in the README.
Cheers,
Bas.
On 20 Jun 2007, at 10:08, Bas Scheffers wrote:
On 20 Jun 2007, at 09:36, Dossy Shiobara wrote:
Hey everyone! Look at Bas, planting the seed for the Year 2033 bug!
Haha! yeah, you have a valid point. But I didn't do it, some dude
at Netscape in 1995 did! AOL bought Netscape, you work for AOL, so
it is all your fault, really! :P
There are two RFCs concerning cookies that address the problem of
needing hard expiry times (as set by the Netscape spec) but from
what I read, they may not be well supported by all clients. For
now, the netscape spec works reliable as long as you don't do
stupid things like setting the expire one hour into the future; if
the user's computer clock is off your application might well not
work at all. Either go for a session cookie, or set it to expire
many years into the future.
Cheers,
Bas.
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to
<[EMAIL PROTECTED]> with the
body of "SIGNOFF AOLSERVER" in the email message. You can leave the
Subject: field of your email blank.
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]>
with the
body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject:
field of your email blank.
