Closed Bug 664959 Opened 15 years ago Closed 12 years ago

On cookie security issues

Categories

(Core :: Networking: Cookies, defect)

x86
Windows XP
defect
Not set
major

Tracking

()

RESOLVED INVALID

People

(Reporter: lrfz111, Unassigned)

Details

User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:2.0.1) Gecko/20100101 Firefox/4.0.1 Build Identifier: Mozilla/5.0 (Windows NT 5.1; rv:2.0.1) Gecko/20100101 Firefox/4.0.1 We assume that the server time serverTime (s), the client is clientTime Server set a cookie valid for half an hour Then the cookie is valid for the client (Time +1800) s Rather than (clientTime +1800) s Reproducible: Always Steps to Reproduce: 1.Set server time 2011-06-17 15:00:00, client time to 2011-06-17 16:00:00 2.Server (setcookie) set the cookie is valid for time (2011-06-17 15:00:00) +1800 s The cookie expires at 2011-06-17 15:30:00 3.cookie on the client is still valid, and the client time is 2011-06-17 16:00:00 Actual Results: cookie on the client is still valid, and the client time is 2011-06-17 16:00:00 Expected Results: cookie should be expired, should be set to invalid
Your steps are unclear, could you please paste the SetCookie: header that your server is sending? Are you using Expires (which has a timezone) or max-age (number of seconds)?
Group: core-security
Component: Security → Networking: Cookies
Product: Firefox → Core
QA Contact: firefox → networking.cookies
(In reply to comment #1) > Your steps are unclear, could you please paste the SetCookie: header that > your server is sending? Are you using Expires (which has a timezone) or > max-age (number of seconds)? My server timezone is Eight districts in East (PRC) The header: Server nginx/0.7.61 Date Thu, 23 Jun 2011 02:40:27 GMT Content-Type text/html Transfer-Encoding chunked Connection keep-alive Vary Accept-Encoding X-Powered-By PHP/5.2.10 Set-Cookie test_cookie=test; expires=Thu, 23-Jun-2011 02:45:27 GMT; path=/; domain=test.com Content-Encoding gzip The header: Date Thu, 23 Jun 2011 02:40:27 GMT and my client time is Thu,23 Jun 2011 10:45:27 PRC
>>Comment2 sorry my client time is Thu,23 Jun 2011 10:50:27 PRC
You mean that the server sets a wrong epire time ? Note: The cookie request from the server contains an absolute time/date I fail to see how this is a client side bug as we get an explicit time when we should expire the cookie
(In reply to Matthias Versen [:Matti] from comment #4) > I fail to see how this is a client side bug as we get an explicit time when > we should expire the cookie invalid per comment 4
Status: UNCONFIRMED → RESOLVED
Closed: 12 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.