I have a separate web server host with a page setting a cookie with an expiration of +5 minutes. Safari would not except this cookie at all while Mozilla would and examining the cookie in Mozilla would show the cookie had an expiration of about 5 minutes in the future. Using another cgi program with the exact same login script, but with +1day expiration worked fine in Safari. This clued me in to a possible explanation. Safari was using the other host's clock (slow by an hour) for setting the relative offset when it should be using it's own host clock!
Reporter, do you have a way for us to reproduce this issue?
(In reply to comment #1) > Reporter, do you have a way for us to reproduce this issue? > [Safari Version 2.0.4 (419.3),PPC,10.4] We have a server with a site and it's clock is set to GMT(UTC). We are in GMT+1 time zone, and using a cookie which should time out after 1 hour. When I do something (log in), cookie is set (is visible in the cookie list in setting), but after closing the session it vanishes. The same would happen it the client's time would be one hour in the future.
(In reply to comment #2) > When I do something (log in), cookie is set (is visible in the cookie list in > setting), but after closing the session it vanishes. How are you "closing the session"? Are you quitting the browser, or logging out of the site? I recall that setting a certain flag on a cookie (security?) will prevent it from being persisted to disk, e.g., it's only stored in memory, so that when the browser quits it will be removed.
No response in a long time, closing. In any case, cookie handling is not part of open source WebKit, so bugs should be filed to Apple via <http://bugreport.apple.com>.