Security Considerations for Optimistic Protocol Transitions in HTTP/1.1
RFC 9931
Revision differences
Document history
| Date | By | Action |
|---|---|---|
|
2026-05-20
|
(System) | Changed metadata: changed keywords to '['Request Smuggling', 'False Start', 'HTTP CONNECT']' from '[]' |
|
2026-05-20
|
(System) | Metadata update from RFC Editor |
|
2026-05-20
|
(System) | Changed author "B. Schwartz": changed name from "Benjamin Schwartz" to "B. Schwartz" |
|
2026-05-20
|
(System) | Metadata update from RFC Editor |
|
2026-03-06
|
(System) | Received changes through RFC Editor sync (created document RFC 9931, created became rfc relationship between draft-ietf-httpbis-optimistic-upgrade and RFC 9931, set abstract to 'In … Received changes through RFC Editor sync (created document RFC 9931, created became rfc relationship between draft-ietf-httpbis-optimistic-upgrade and RFC 9931, set abstract to 'In HTTP/1.1, the client can request a change to a new protocol on the existing connection. This document discusses the security considerations that apply to data sent by the client before this request is confirmed and adds new requirements to RFCs 9112 and 9298 to avoid related security issues.', set pages to 11, set standardization level to Proposed Standard, added RFC published event at 2026-03-06, created updates relation between RFC 9931 and RFC 9112, created updates relation between RFC 9931 and RFC 9298) |
|
2026-03-06
|
(System) | RFC published |