From d0e78ca5c6abb75b306e669ed844dd3705992677 Mon Sep 17 00:00:00 2001 From: Marcos Casagrande Date: Mon, 17 Oct 2022 15:39:41 +0200 Subject: fix(ext/fetch): set accept-encoding: identity if range header is present (#16197) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit https://fetch.spec.whatwg.org/#http-network-or-cache-fetch > If httpRequest’s header list contains `Range`, then append (`Accept-Encoding`, `identity`) > to httpRequest’s header list. > > This avoids a failure when handling content codings with a part of an encoded response. > Additionally, many servers mistakenly ignore `Range` headers if a non-identity encoding is accepted. --- tools/wpt/expectation.json | 2 -- 1 file changed, 2 deletions(-) (limited to 'tools/wpt') diff --git a/tools/wpt/expectation.json b/tools/wpt/expectation.json index d713775d0..a3dcaa70c 100644 --- a/tools/wpt/expectation.json +++ b/tools/wpt/expectation.json @@ -3266,12 +3266,10 @@ "range": { "general.any.html": [ "Privileged header not allowed for guard type: request-no-cors", - "Fetch with range header will be sent with Accept-Encoding: identity", "Cross Origin Fetch with non safe range header" ], "general.any.worker.html": [ "Privileged header not allowed for guard type: request-no-cors", - "Fetch with range header will be sent with Accept-Encoding: identity", "Cross Origin Fetch with non safe range header" ], "general.window.html": false -- cgit v1.2.3