Security Considerations for Optimistic Use of HTTP Upgrade
draft-schwartz-httpbis-optimistic-upgrade-00
| Document | Type |
Replaced Internet-Draft
(httpbis WG)
Expired & archived
|
|
|---|---|---|---|
| Author | Benjamin M. Schwartz | ||
| Last updated | 2024-02-22 (Latest revision 2023-08-21) | ||
| Replaced by | draft-ietf-httpbis-optimistic-upgrade | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | Adopted by a WG | |
| Document shepherd | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-httpbis-optimistic-upgrade | |
| Consensus boilerplate | Unknown | ||
| 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
The HTTP/1.1 Upgrade mechanism allows the client to request a change to a new protocol. This document discusses the security considerations that apply to data sent by the client before this request is confirmed, and updates RFC 9298 to avoid related security issues.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)