Re: [whatwg/fetch] Add new Access-Control-Suppress-Headers CORS response header (#253)

> By allowing those developers to explicitly define which headers should be hidden from client-side code, it gives them the ability to not worry about having to explicitly add new headers to the Access-Control-Expose-Headers 'list'.

Conversely, it allows those developers to footgun themselves by adding a new sensitive header and forgetting to update the AC-Suppress-H list. If your application needs the data you'll quickly figure it out if you forget to update ACEH; forgetting to update ACSH leads to a security vulnerability. A long and painful history teaches us that forgetting is likely either way. We strongly lean towards causing work for developers versus trouble for everyone.



---
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/253#issuecomment-217049052