Re: [whatwg/fetch] Change how CORS filtered response filters the headers. (#265)

> -   <dd><span title=concept-filtered-response-basic>basic filtered response</span>
> -   <dt>"<code title>cors</code>"
> -   <dd><span title=concept-filtered-response-cors>CORS filtered response</span>
> -   <dt>"<code title>opaque</code>"
> -   <dd><span title=concept-filtered-response-opaque>opaque filtered response</span>
> -  </dl>
> +  <span title=concept-filtered-response>filtered response</span>, run these substeps:
> +
> +  <ol>
> +   <li>
> +    <p>Set <var>response</var>'s
> +    <span title=concept-response-cors-exposed-header-name-list>CORS-exposed header-name list</span>
> +    to the result of <span title=concept-header-parse>parsing</span>
> +    `<code title=http-access-control-expose-headers>Access-Control-Expose-Headers</code>` in
> +    <var>response</var>'s
> +    <span title=concept-response-header-list>header list</span>.

Although it does not matter in a black-box observable way, I still think we should add a conditional here for response tainting being "cors".

---
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/265/files/25a6c07fdf625537d8c0c69fd4ad53bbf4086d7c#r57839388