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

I am not against a dedicated getter within the Headers class.
That said, I'd like to mention the potential complexity for implementors: Cache API as well as exposing a request to service worker fetch event handler might need specific handling to preserve Set-Cookie headers, depending on the actual underlying implementation.
It is unclear to me how valuable an addition this is to the web platform (are we talking about setting Set-Cookie to request headers?).

-- 
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-960752839