Closed
Bug 1256007
Opened 8 years ago
Closed 4 years ago
Cookie Expiration
Categories
(Testing :: General, defect)
Tracking
(Not tracked)
RESOLVED
INACTIVE
People
(Reporter: titus.fortner, Unassigned)
Details
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/48.0.2564.116 Safari/537.36 Steps to reproduce: Created a cookie with an expiry value as an integer, then got the list of cookies I used unix epoch time as an integer per: https://w3c.github.io/webdriver/webdriver-spec.html#dfn-cookie-expiry-time Debug - https://gist.github.com/titusfortner/422333ac96591f60a3c0 Actual results: cookie returned had an expiration of null Expected results: cookie returned should have had the expiration set
Reporter | ||
Comment 1•8 years ago
|
||
I'm still seeing this on FF 50 -> POST session/71dfa503-63b8-f54b-b632-12c67a85d361/cookie >>> http://127.0.0.1:4445/session/71dfa503-63b8-f54b-b632-12c67a85d361/cookie | {"cookie":{"name":"foo","value":"bar","path":"/","secure":false,"expiry":2177452800}} <- {} -> GET session/71dfa503-63b8-f54b-b632-12c67a85d361/cookie <- {"value":[{"name":"foo","value":"bar","path":"/","domain":"localhost","expiry":null,"secure":false,"httpOnly":false}]}
Reporter | ||
Comment 2•7 years ago
|
||
Per the spec expiry should be returned with: "The value if the entry exists, otherwise a Unix timestamp 20 years into the future from now." As it stands, I never get an expiry returned, regardless of whether or not it is passed in. https://gist.github.com/titusfortner/1941569a30fbd02853e743b0cce14349 Firefox 53.0a1 (2017-01-08) (64-bit) Geckodriver 0.13.0
Reporter | ||
Comment 3•7 years ago
|
||
No expiry returned issue still present in Firefox 54 & Geckodriver 0.14.0
Version: 45 Branch → 54 Branch
Updated•4 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 4 years ago
Resolution: --- → INACTIVE
You need to log in
before you can comment on or make changes to this bug.
Description
•