Re: [fetch] Introduce HTTP-redirect fetch (#194)

> +<var>request</var> and <var>response</var>, with an optional <i>CORS flag</i>, run these steps:
> +
> +<ol>
> + <li><p>Let <var>actualResponse</var> be <var>response</var>, if <var>response</var> is not a
> + <a href="#concept-filtered-response" title="concept-filtered-response">filtered response</a>, and <var>response</var>'s
> + <a href="#concept-internal-response" title="concept-internal-response">internal response</a> otherwise.
> +
> + <li><p>Let <var>location</var> be the result of <a href="#concept-header-parse" title="concept-header-parse">parsing</a>
> + `<code title="">Location</code>` in <var>actualResponse</var>'s
> + <a href="#concept-response-header-list" title="concept-response-header-list">header list</a>.
> +
> + <li><p>If <var>location</var> is null, return <var>response</var>.
> +
> + <li><p>If <var>location</var> is failure, return a
> + <a href="#concept-network-error" title="concept-network-error">network error</a>.
> + <!-- only Gecko does this; and even that is currently more complicated -->

Interesting, what do the other browsers do?

---
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/pull/194/files#r51467375