HTTP Alternative Services That Do Not Support Desired Extensions
draft-pardue-alt-svc-ext-unsupported-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Lucas Pardue | ||
| Last updated | 2021-01-14 (Latest revision 2020-07-13) | ||
| 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
This document describes an error case when an HTTP Alternative Service does not support the extension points of the original connection. It defines an error code that can be used by endpoints to signal the encounter.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)