GoFuckYourself.com - Adult Webmaster Forum - View Single Post - PHP Cook-ies Max-Age WRONG!?

mryellow · 08-14-2004, 09:36 PM

PHP's setcookie function seems to be wrong....

It used to be that you'd set cookies based on a GMT general date
format. However this wasn't affective as there is no way you can
set a client to expire based on the server time as there is little
chance of them being the same.

So the standard was changed to "Max-Age" being "Seconds till
expire". However the PHP manual states that it's "Seconds since
Epoch (1/1/1970)". Which still creates the client/server conflict in
time settings.

Is the PHP manual wrong?
or
Is PHP wrong?
or
Is does it work as it should?
Meaning you just set the number of seconds to expiry.

-Ben

08-14-2004, 09:36 PM
mryellow Confirmed User Industry Role: Join Date: May 2001 Location: Australia Posts: 934	PHP Cook-ies Max-Age WRONG!? PHP's setcookie function seems to be wrong.... It used to be that you'd set cookies based on a GMT general date format. However this wasn't affective as there is no way you can set a client to expire based on the server time as there is little chance of them being the same. So the standard was changed to "Max-Age" being "Seconds till expire". However the PHP manual states that it's "Seconds since Epoch (1/1/1970)". Which still creates the client/server conflict in time settings. Is the PHP manual wrong? or Is PHP wrong? or Is does it work as it should? Meaning you just set the number of seconds to expiry. -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.