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

> 1. Tests need to be written in web-platform-tests to ensure the header does not get overwritten when set directly.

It doesn't look like web-platform-tests support HTTP/3 which is where it is commonly used. I can create HTTP/1 and HTTP/2 tests which will test one of Chrome's paths but I'm not sure it will work for either Firefox or Safari (as best as I could tell, the change in Firefox 126 is still only setting the header in HTTP/3).

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

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

Received on Monday, 3 June 2024 14:12:34 UTC