fetch: add an accept encoding header when the range header exists (#33496)

Signed-off-by: Shane Handley <shanehandley@fastmail.com>
This commit is contained in:
shanehandley 2024-09-19 21:35:52 +10:00 committed by GitHub
parent 05b2aa29c3
commit 06f0893b94
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
5 changed files with 32 additions and 31 deletions

View file

@ -5,9 +5,6 @@
[general]
expected: FAIL
[Fetch with range header will be sent with Accept-Encoding: identity]
expected: FAIL
[Cross Origin Fetch with safe range header]
expected: FAIL
@ -19,9 +16,6 @@
[general]
expected: FAIL
[Fetch with range header will be sent with Accept-Encoding: identity]
expected: FAIL
[Cross Origin Fetch with safe range header]
expected: FAIL

View file

@ -4,6 +4,3 @@
[general]
expected: FAIL
[Fetch with range header will be sent with Accept-Encoding: identity]
expected: FAIL

View file

@ -2,9 +2,6 @@
expected: ERROR
[general.any.html]
[Fetch with range header will be sent with Accept-Encoding: identity]
expected: FAIL
[Cross Origin Fetch with safe range header]
expected: FAIL
@ -13,8 +10,5 @@
expected: ERROR
[general.any.worker.html]
[Fetch with range header will be sent with Accept-Encoding: identity]
expected: FAIL
[Cross Origin Fetch with safe range header]
expected: FAIL

View file

@ -1,3 +0,0 @@
[general.window.html]
[Fetch with range header will be sent with Accept-Encoding: identity]
expected: FAIL