[Webkit-unassigned] [Bug 26193] Incorrect server time invalidates cookies

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Wed Feb 9 17:19:48 PST 2011


https://bugs.webkit.org/show_bug.cgi?id=26193





--- Comment #5 from Alexander Romanovich <alex at sirensclef.com>  2011-02-09 17:19:48 PST ---
(In reply to comment #3)
> > Is it possible that Firefox is getting the server's reported time, calculating an offset before server time and client time, and then dynamically adjusting the cookie expiration time accordingly? My mind is boggled a little bit.
> 
> Yes, but Firefox is the only browser that does this.  We discussed the issue in the cookie working group at the IETF and they agreed to remove this behavior because it's super nutty.

Do you mean Firefox has agreed to remove this behavior? I'm less interested in having Safari match FF's behavior as I am seeing all browser vendors handle the situation the same way. That will help remove ambiguity for us developers.

At least in my experience it probably would have resulted in the issue being more quickly recognized as a server misconfiguration than an incompatibility with the Safari browser as it was originally reported to us. I'd love to look into getting the behavior standardized (with Safari's behavior, as agreed upon by the cookie working group), whether that means going to W3C or the Firefox team. But if there's already action being taken, I won't bother.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.



More information about the webkit-unassigned mailing list