Bug 15128 - ER: Set-Cookie header field (RFC 2109) not supported correctly
Summary: ER: Set-Cookie header field (RFC 2109) not supported correctly
Status: RESOLVED INVALID
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebCore Misc. (show other bugs)
Version: 528+ (Nightly build)
Hardware: All All
: P4 Enhancement
Assignee: Nobody
URL: http://www.ietf.org/rfc/rfc2109.txt
Keywords: InRadar
Depends on:
Blocks:
 
Reported: 2007-09-01 11:38 PDT by Markus Wulftange
Modified: 2008-03-18 14:28 PDT (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Markus Wulftange 2007-09-01 11:38:25 PDT 
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.
Comment 1 Alexey Proskuryakov 2007-09-01 12:38:21 PDT 
Does this work in other browsers?
Comment 2 Markus Wulftange 2007-09-01 13:08:22 PDT 
In Opera 9.22 this works correctly.
Comment 3 David Kilzer (:ddkilzer) 2007-10-05 08:57:47 PDT 
<rdar://problem/5524766>
Comment 4 Robert Blaut 2008-03-18 13:42:43 PDT 
Confirmed as an enhancement request.
Comment 5 Alexey Proskuryakov 2008-03-18 14:28:52 PDT 
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.