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

@annevk do you have suggestions on how the process flow would look when the value of the `Priority` header itself is decided and defined at transport-time and the actual priority values are internal breowser-specific (and a bit opaque in the spec)?

I could see something like "If httpRequest’s header list does not contain 'Priority', then user agents may append an appropriate Priority to httpRequest’s header list." but the steps for determining the value to set would require unwinding the browser-specific treatment of [internal-priority](https://fetch.spec.whatwg.org/#request-internal-priority).

Maybe a some text that references the extensible priorities RFC and call it a mapping of internal-priority to the RFC?

The timing of the processing might not be appropriate though (as we move towards browser literally implementing the process steps directly) and maybe something like a boolean flag on request that indicates if the `Priority` header is allowed to be set by the transport layer or not and leave the actual setting opaque?

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

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