Re: [whatwg/fetch] Allowed header in CORS with Access-Control-Expose-Headers (#369)

May be I have the wrong wording. What I wanted to express was that other than the safe listed headers if you want to have your custom header available for the web client, you can send that header name in `Access-Control-Expose-Headers ` header.

For example, Lets say the server wants the clients to be able to access header `A` of the response of a CORS request. Server can send `Access-Control-Expose-Headers : A` on the response and the fetch implementation makes the header available through `response.headers.get('A')`.


-- 
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/pull/369#issuecomment-240158593