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

Yeah, I think this is worth doing, especially for iteration as it seems rather bad if that behaves differently depending on where you run the code. I also saw an argument by @domenic that `Headers` is a generic data structure and therefore should have `[Exposed=*]` which I think also argues for handling `Set-Cookie` correctly.

Having said that, we need a better solution when `Headers`'s guard is "`request`" as requiring a more complicated data structure in that case does not carry its weight I think, especially given that `Set-Cookie` is a response header. The simplest solution would be making `Set-Cookie` a forbidden header name, but that probably requires experimenting whether that breaks any unusual code out there.

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