Declaring Support for HTTP/2 Priorities
draft-lassey-priority-setting-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Bradford Lassey , Lucas Pardue | ||
| Last updated | 2020-01-26 (Latest revision 2019-07-25) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
HTTP/2 provides a prioritization scheme but experience has shown that implementation support varies. This document defines an HTTP/2 setting that endpoints can use as an affirmative signal to indicate their support for HTTP/2 Priorities.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)