Re: [whatwg/fetch] Allow range header to be set by APIs (#560)

Certainly no harm in it. I'll do that.

On Fri, 18 May 2018 at 16:11, Anne van Kesteren <notifications@github.com>
wrote:

> *@annevk* commented on this pull request.
> ------------------------------
>
> In fetch.bs
> <https://github.com/whatwg/fetch/pull/560#discussion_r189301239>:
>
> > @@ -2911,6 +2972,39 @@ with a <i>CORS flag</i> and <i>recursive flag</i>, run these steps:
>     <li><a lt="should response to request be blocked due to nosniff">should <var>internalResponse</var> to <var>request</var> be blocked due to nosniff</a>
>    </ul>
>
> + <li>
> +  <p>If <var>internalResponse</var>'s <a for=response>status</a> is <code>206</code>,
> +  <var>response</var>'s <a for=response>type</a> is "<code>opaque</code>",
> +  <var>internalResponse</var>'s <a for=response>range-requested flag</a> is set, and
> +  <var>request</var>'s <a for=request>header list</a> does not <a for="header list">contain</a>
> +  `<code>Range</code>`, then:
> +
> +  <ol>
> +   <li><p>Set <var>internalResponse</var> to a new <a for=/>response</a>.
> +
> +   <li><p>Set <var>response</var>'s <a>internal response</a> to <var>internalResponse</var>.
>
> I think reusing the CORB strategy is probably better (by abstracting the
> way it replaces the response so it can be reused here), since I think we
> want them to be equivalent. But maybe I'm missing something?
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <https://github.com/whatwg/fetch/pull/560#discussion_r189301239>, or mute
> the thread
> <https://github.com/notifications/unsubscribe-auth/AAFtml9nJCRuE65mo-oJlyTWcmRFgtkfks5tzuSXgaJpZM4OJjO_>
> .
>


-- 
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/560#issuecomment-390239200