On Tue, Oct 10, 2023 at 8:27 AM Alex Russell <slightly...@chromium.org> wrote:
> Why has this not been sent to the TAG? > There's no TAG requirement for an I2E, and this is defined as part of the IETF, so outside of the TAG's "jurisdiction". > > On Mon, Oct 9, 2023, 1:40 PM Patrick Meenan <pmee...@chromium.org> wrote: > >> Contact emailspmee...@google.com >> >> ExplainerNone >> >> Specificationhttps://datatracker.ietf.org/doc/rfc9218 >> >> Summary >> >> This feature adds the 'priority' request header for all HTTP requests >> with the priority information for the request at the time that it was sent. >> RFC 9218 (Extensible Prioritization Scheme for HTTP) defines a 'priority' >> HTTP request header to use for signaling request priority to origins (and >> intermediaries). It also defines negotiation processes and protocol-level >> frames for HTTP/2 and HTTP/3 to carry the same priority information. The >> header can only signal the initial priority for a resource when it was >> first requested while the frame-based mechanisms allow for modifying the >> priority after the fact. The header can operate end-to-end to the origin >> servers (and provide a mechanism for the origin to override the priority if >> recognized by intermediaries) while the frames are limited to operating on >> a link level. This feature is specifically for supporting the header-based >> prioritization scheme. >> >> >> Blink componentBlink>Network >> <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3ENetwork> >> >> TAG reviewNone >> >> TAG review statusNot applicable >> >> Risks >> Interoperability and Compatibility >> >> None >> >> *Gecko*: Shipped/Shipping >> *WebKit*: Shipped/Shipping >> *Web developers*: No signals >> *Other signals*: >> >> Security >> >> The priority information for a given request is already exposed in HTTP/2 >> and HTTP/3 in the frame-based priority fields (and weights in HTTP/2). This >> moves the same information directly into the headers for HTTP/2 and HTTP/3 >> only. >> >> WebView application risks >> >> Does this intent deprecate or change behavior of existing APIs, such that >> it has potentially high risk for Android WebView-based applications? >> >> None >> >> Goals for experimentation >> >> Enable the header for a sample of the population and make sure there is >> no negative feedback before turning on globally. >> >> Ongoing technical constraints >> >> None >> >> Debuggability >> >> The "Priority" header is exposed in both the Dev Tools network panel (in >> the Request Headers) and in the Netlog. >> >> Will this feature be supported on all six Blink platforms (Windows, Mac, >> Linux, Chrome OS, Android, and Android WebView)?Yes >> >> Is this feature fully tested by web-platform-tests >> <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md> >> ?No >> >> HTTP headers (and protocols) are not testable in Web Platform Tests. >> >> >> Flag name on chrome://flags >> >> Finch feature namePriorityHeader >> >> Requires code in //chrome?False >> >> Tracking bughttps://bugs.chromium.org/p/chromium/issues/detail?id=1404785 >> >> Estimated milestones >> DevTrial on desktop 119 >> DevTrial on Android 119 >> Link to entry on the Chrome Platform Status >> https://chromestatus.com/feature/5109106573049856 >> >> Links to previous Intent discussionsIntent to prototype: >> https://groups.google.com/a/chromium.org/g/blink-dev/c/eEeDzwtw5v0 >> >> This intent message was generated by Chrome Platform Status >> <https://chromestatus.com/>. >> >> -- >> You received this message because you are subscribed to the Google Groups >> "blink-dev" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to blink-dev+unsubscr...@chromium.org. >> To view this discussion on the web visit >> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAPq58w5KJijit8ObBhWKzCnLjro7jSfAsxfPPZ66NwmTO_ZT%3Dg%40mail.gmail.com >> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAPq58w5KJijit8ObBhWKzCnLjro7jSfAsxfPPZ66NwmTO_ZT%3Dg%40mail.gmail.com?utm_medium=email&utm_source=footer> >> . >> > -- > You received this message because you are subscribed to the Google Groups > "blink-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to blink-dev+unsubscr...@chromium.org. > To view this discussion on the web visit > https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAA44PQiO3mJB-NnBPaDU6fNTHNzxgy%2B-%3D-Proz-sGZVVgVk-MA%40mail.gmail.com > <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAA44PQiO3mJB-NnBPaDU6fNTHNzxgy%2B-%3D-Proz-sGZVVgVk-MA%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscr...@chromium.org. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAL5BFfWHuuWN5%2BzpZs2uNDyzVY23vDUZ%3D08dJsLUdvsqE-tYGw%40mail.gmail.com.
