Visual RFC.
ALL RFCs / RFC 9114
Read the RFC ↗
RFC 9114 / MECHANISM GUIDE

Push and connection shutdown

05

Push promises and shutdown have explicit identifiers and limits.

Related RFCs and changes

“Updates” changes part of an earlier RFC. “Obsoletes” replaces it. This list shows selected related documents.

DIAGRAM§ 5.2 ↗
RFC 9114 · § 5.2EXAMPLE
3 / 3
Push and connection shutdownPush promises and shutdown have explicit identifiers and limits.Push and connection shutdownClient permits push IDs through 2MAX_PUSH_ID2PUSH_PROMISE: ID 1 → /style.cssGOAWAY: no requests at or beyond the limit
03
Send GOAWAY

Stop initiating requests beyond the indicated acceptance limit.

Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
KEY POINT

Server push requires client permission through MAX_PUSH_ID.

  • Server push requires client permission through MAX_PUSH_ID.
  • GOAWAY limits future request acceptance and supports orderly shutdown.
  • Rejected and cancelled requests need outcome-aware retry handling.
DETAILS

Examples are illustrative. Consult the linked RFC and its errata for implementation details.

Read the RFC section ↗

Diagrams simplify the RFC. Read the linked sections for complete requirements.

Privacy
All chapters in this RFC
  1. HTTP over QUIC
  2. Request frame order
  3. Critical control streams
  4. QPACK and blocked fields
  5. Push and connection shutdown
RFC 9700 / CHAPTERS

Chapters

For full details, tables, algorithms, and exceptions, read the original RFC.

RFC status and corrections ↗