Acceptance criteria
For folks helping with Firefox related documentation
Features to document
I am not entirely sure what is relevant and what needs to be documented. However the spec indicates a new Priority HTTP header (possibly HTTP3 only) in https://www.rfc-editor.org/rfc/rfc9218.html#section-5 and we generally document those.
This also disables the previous HTTP/2 approach defined in network.http.http2.enabled.deps which does not appear to have any "public" headers.
We also would probably add the spec to https://developer.mozilla.org/en-US/docs/Web/HTTP/Resources_and_specifications
FYI this is enabled by default
- network.http.priority_header.enabled - enables new Priority header from RFC9218
- network.http.http2.enabled.deps - turns off old RFC7540 stream dependencies
More investigation is needed, and there is a little background here: https://blog.cloudflare.com/adopting-a-new-approach-to-http-prioritization/
Related Gecko bugs
1865040: Implement Extensible Prioritization Scheme for HTTP/2
Other
Acceptance criteria
For folks helping with Firefox related documentation
dev-doc-completeFeatures to document
I am not entirely sure what is relevant and what needs to be documented. However the spec indicates a new
PriorityHTTP header (possibly HTTP3 only) in https://www.rfc-editor.org/rfc/rfc9218.html#section-5 and we generally document those.This also disables the previous HTTP/2 approach defined in network.http.http2.enabled.deps which does not appear to have any "public" headers.
We also would probably add the spec to https://developer.mozilla.org/en-US/docs/Web/HTTP/Resources_and_specifications
FYI this is enabled by default
More investigation is needed, and there is a little background here: https://blog.cloudflare.com/adopting-a-new-approach-to-http-prioritization/
Related Gecko bugs
1865040: Implement Extensible Prioritization Scheme for HTTP/2
Other