[Webkit-unassigned] [Bug 251194] New: [fetch] Implement `Headers.prototype.getSetCookie`

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=251194

            Bug ID: 251194
           Summary: [fetch] Implement `Headers.prototype.getSetCookie`
           Product: WebKit
           Version: Other
          Hardware: Unspecified
                OS: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: WebCore Misc.
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: abotella at igalia.com

Spec PR: https://github.com/whatwg/fetch/pull/1346
Test PR: https://github.com/web-platform-tests/wpt/pull/31442

The proposed `getSetCookie()` method of the Headers class allows getting a list of the values of the `Set-Cookie` header in the header list. This was not possible before, since the `get()` method would combine the values by joining them with comma and whitespace, which is valid per the HTTP spec, but clashes with Set-Cookie syntax.

The spec change that introduces this method also changes the iteration behavior for Headers to have each Set-Cookie header show up in the iteration, rather than having them combined.

The fetch spec's `Request` and `Response` classes don't allow setting the `Set-Cookie` header, and `fetch` will remove that header from the returned `Response`. This change to the spec does not change this. It only makes it so a user-created `Headers` class can deal with `Set-Cookie` headers in an easier way, and enables compatibility with server-side runtimes which allow these headers.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20230126/56b75500/attachment.htm>