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

Chrome 124 and Firefox 126 both set the Priority header for HTTP/2 requests, but Safari 17.5 does not.

The Priority header implementation in Chrome and Firefox ignores the existence of the request filtering engine available to extensions. `declarativeNetRequest` and `webRequest` do not see the header because it is set by the browser after request filtering occurs, so extensions cannot remove the header, they will only be able to set a custom value.

Any new HTTP headers you introduce should be set before request filtering, so extensions can have full control over them. If setting the Priority header later on in the network stack is indeed crucial and cannot be done earlier, please reach out to the folks at https://github.com/w3c/webextensions to discuss a solution for having control over such headers.

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

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