| Summary: | ER: Set-Cookie header field (RFC 2109) not supported correctly | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Markus Wulftange <markus.wulftange> |
| Component: | WebCore Misc. | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED INVALID | ||
| Severity: | Enhancement | CC: | ap, mrowe, webkit |
| Priority: | P4 | Keywords: | InRadar |
| Version: | 528+ (Nightly build) | ||
| Hardware: | All | ||
| OS: | All | ||
| URL: | http://www.ietf.org/rfc/rfc2109.txt | ||
Does this work in other browsers? In Opera 9.22 this works correctly. Confirmed as an enhancement request. This issue is in a lower level system framework, not in WebKit. Closing as INVALID per our process; this will continue to be tracked internally by Apple. |
WebKit does not support the Set-Cookie header field correctly as specified in RFC 2109. Consider the following Set-Cookie response header field: Set-Cookie: foo=bar; Version=1; Max-Age=0 Though the Version attribute is set and the Max-Age attribute value is zero (which means the cookie should be discarded immediately) this response header field is treated as a normal "Netscape Cookie" Set-Cookie header field.