ID: 11052
Updated by: rasmus
Reported By: [EMAIL PROTECTED]
Old-Status: Open
Status: Closed
Bug Type: HTTP related
Operating system:
PHP Version: 4.0.5
Assigned To:
Comments:
Perhaps because the clock on that server you are uploading to is off, or maybe your
clock is off. And you are right, this is not a PHP bug. Fix you clock or encode the
server's timestamp in the cookie and check that when it gets the cookie back to
determine if it should still be valid.
Previous Comments:
---------------------------------------------------------------------------
[2001-05-23 08:22:29] [EMAIL PROTECTED]
I am rather sure this isn't a php bug. So lets not get unfriendly about it. But i
have asked over and over in other places with out an answer. at least point me in the
right direction. please
I have set up a user login so that it will assign a cookie for one hour -
setcookie("cookie_id", $id, time()+3600);
The manner in which i suse the expiration is copied form the manual but i have
actually tried several alteratives. The problem is the expiration works perfectly
locally (i am running apache 1.3 for windows) but once i upload it (linux red hat 5.2
(why so old i dont know)/ apache 1.3.19.) The expiration will not work on my
browser(s) unless i increase the expiration to +5000 or above. My client tests it
using the same version of IE i have and it will not set the cookie still at +5000 for
him.
Now i understand from browser to browser there can be differences but why can i set a
cookie for +200 locally but not for less than +5000 uploaded when i am most certainly
checking it with the same browser (IE 5.5)
---------------------------------------------------------------------------
ATTENTION! Do NOT reply to this email!
To reply, use the web interface found at http://bugs.php.net/?id=11052&edit=2
--
PHP Development Mailing List <http://www.php.net/>
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]
