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

> @@ -2036,6 +2040,18 @@ <h4 id="should-response-to-request-be-blocked-due-to-nosniff?"><dfn title="shoul
>    <span title=concept-network-error>network error</span> and
>    <var>response</var> is not a
>    <span title=concept-filtered-response>filtered response</span>, set
> +  <var>response</var>'s
> +  <span title=concept-response-cors-exposed-headers-list>CORS-exposed headers 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>.
> +
> + <li>
> +  <p>If <var>response</var> is not a
> +  <span title=concept-network-error>network error</span> and
> +  <var>response</var> is not a
> +  <span title=concept-filtered-response>filtered response</span>, set

I think we should try to find a solution that creates a CORS filtered response in a single step. Or at least a set of steps that belong together. E.g., the check for network error and filtered response is only needed once, you could then run substeps. But maybe there's a way to do the `<dl>` differently as well that cleans this up a bit.

---
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/8c2a9dd538585584b4caeaa93f3c1f1e8b5a6239#r57690941