|
try time()+$secs is wrong.
time() is on the server. The cookie is expiring on the client.
How can you set the expiry based on Epoch if the server and
client time are not exactly the same.... You can't... Thus they
changed the specifications and instead of using "Expires" (GMT
general date) they now use "Max-Age" (seconds TILL EXPIRY)....
Whereas the manual states it is "seconds since Epoch" which is
wrong.
There are crap-loads of ppl writting all sorts of stupid functions to
properly handle this when the only real problem is the manual
has false information.
It seems this false information is so well spread that netscape
even accounts for it and will use either the correct or incorrect
method for expiry time by checking the server time against that of
the client. However I believe this is the only browser which does
such. Man there must be a LOT of people out there with incorrect
cookie code.
-Ben
__________________
Cyberwurx Hosting
After trying 5 different hosts, I found the best.
Since 1997 I've had 2 hours of downtime.
Fast support, great techs, no hype, no gimmicks.
<- I in no way endorse whatever just got stuck on the left of my post.
|