Re: [whatwg/fetch] Use case for Headers getAll (#973)

> that probably requires experimenting whether that breaks any unusual code out there.

It would make sense to do that experiment before proceeding with fetch spec changes.

Or getSetCookie API could be defined for non-browser-env only (say partial interface with [Exposed=non-browser-env]) in an extension spec, until we know it is safe to make Set-Cookie a forbidden header name on web environments.
https://github.com/whatwg/fetch/pull/1346 could be split in two: infra part remaining in fetch spec, API going in an extension spec.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/issues/973#issuecomment-961918685