Re: [fetch] Update Access-Control-Expose-Headers CORS response header to allow * (allow-all) (#252)

Implementers have traditionally been wary about doing this, since it could be a footgun. Servers might have forgotten about certain debug headers exposing information that was meant to be kept secret, etc.

@sicking @tyoshino?


---
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/252#issuecomment-198234273