Re: [whatwg/fetch] Define behavior for `Priority` request header (Issue #1718)

> > At least in the case of Chrome, if the Priority header is set before it gets to the networking stack then the user-supplied value will be used (like was discussed above).
> 
> Starting with Firefox 126 we send the header for all requests, and override any user set header: https://phabricator.services.mozilla.com/D201265 We're happy to align on the Chrome behaviour, as stated above. I filed [1900362](https://bugzilla.mozilla.org/show_bug.cgi?id=1900362) to do just that.

While working on bug [1900362](https://bugzilla.mozilla.org/show_bug.cgi?id=1900362), we found that we need to include the `priority` header in the [CORS-safelisted request-header](https://fetch.spec.whatwg.org/#cors-safelisted-request-header) list to pass some tests. I'm not sure if we implemented it incorrectly or if the `priority` header actually needs to be in the list.

@annevk , what do you think?
Thanks.

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

Message ID: <whatwg/fetch/issues/1718/2191084565@github.com>