Bug 26250
| Summary: | If cookie string assigned to document.cookie has "expires" no greater than 3600 seconds from now, the cookie is not changed. | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Morgan Cheng <morgan_cheng> |
| Component: | WebCore Misc. | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED INVALID | ||
| Severity: | Normal | CC: | ap, aroben |
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | PC | ||
| OS: | Windows Vista | ||
Morgan Cheng
Below script demo this issue.
If document.cookie is assigned a cookie with expires no greater than 1 hour (3600 seconds) from now, the cookie is not set. If expires is greater than 3600 seconds, it works.
<body>
<script>
var dt = new Date();
dt.setSeconds(dt.getSeconds() + 3600);
document.cookie = "cookietest=1; expires=" + dt.toGMTString();
var cookiesEnabled = document.cookie.indexOf("cookietest=") != -1;
alert(document.cookie);
alert(cookiesEnabled);
</script>
</body>
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Adam Roben (:aroben)
Morgan, does this issue still occur in the final release of Safari 4 for Windows? If it only occurs in Safari 4 Public Beta for Windows, then it is caused by a bug in CFNetwork (tracked by <rdar://problem/6772112>), which is also the root cause of bug 25861.
Gavin Barraclough
This is not a JSC bug, moving to the misc component.
Alexey Proskuryakov
No answer in more than 3 years, marking INVALID. Please feel free to re-open if you have additional information, or to open a new bug if you are seeing something similar, but not necessarily the same issue.