Re: [whatwg/fetch] Add `range` to CORS-safelisted request-headers (#1310)

I just tried your snippet, and I think there is indeed something wrong.  The Range header is not sent at all with `mode: 'no-cors'`, but is if I omit that.

However, you should also know that your chosen URL does an HTTP 302 redirect, but browsers don't transfer `Range` headers when following redirects.

That said, I can reproduce your issue with other URLs that don't redirect.  For example:


```js
// Works
fetch('https://ajax.googleapis.com/ajax/libs/shaka-player/4.3.8/shaka-player.compiled.js', {
  headers: {
    Range: 'bytes=0-10240'
  }
})
```

```js
// Ignores Range header
fetch('https://ajax.googleapis.com/ajax/libs/shaka-player/4.3.8/shaka-player.compiled.js', {
  mode: 'no-cors',
  headers: {
    Range: 'bytes=0-10240'
  }
})
```

I'm no expert, but this certainly breaks my expectations.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/issues/1310#issuecomment-2291734217
You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/fetch/issues/1310/2291734217@github.com>