From 2f3d04d3713f6cd0f89d491217175b55911927be Mon Sep 17 00:00:00 2001 From: Jake Archibald Date: Wed, 6 Jun 2018 08:26:21 +0100 Subject: [PATCH] Specify identity encoding for range requests Tests: https://github.com/web-platform-tests/wpt/pull/11291. Fixes #747. --- fetch.bs | 15 +++++++++++++-- 1 file changed, 13 insertions(+), 2 deletions(-) diff --git a/fetch.bs b/fetch.bs index be1fd4918..9468109d0 100644 --- a/fetch.bs +++ b/fetch.bs @@ -3652,8 +3652,19 @@ Range Requests. [[HTTP-RANGE]] However, this is not widely supported by b
  • -

    Modify httpRequest's - header list per HTTP. +

    If httpRequest's header list contains + `Range`, then append + `Accept-Encoding`/`identity` to httpRequest's + header list. + +

    Many servers + mistakenly ignore `Range` headers if a non-identity encoding is accepted. + +

  • +

    Modify httpRequest's header list per HTTP. Do not + append a given header if httpRequest's + header list contains that header's + name.

    It would be great if we could make this more normative somehow. At this point headers such as