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

Reset and graceful shutdown

05

A broken stream and a broken connection require different signals.

Related RFCs and changes

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

DIAGRAM§ 5.4 ↗
RFC 9113 · § 5.4EXAMPLE
3 / 3
Reset and graceful shutdownA broken stream and a broken connection require different signals.Reset and graceful shutdown1HEADERSDATAEND3HEADERSRST_STREAM 3 does not reset stream 1GOAWAY: last processed stream = 3
03
Send GOAWAY

The last-stream identifier bounds which requests may have been processed.

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

RST_STREAM terminates the named stream without closing every other stream.

  • RST_STREAM terminates the named stream without closing every other stream.
  • GOAWAY communicates connection shutdown and a last-stream identifier.
  • Do not blindly retry non-idempotent work whose outcome is uncertain.
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. Connection preface
  2. Multiplexed streams
  3. Frames and compressed fields
  4. Receiver flow-control credit
  5. Reset and graceful shutdown
RFC 9700 / CHAPTERS

Chapters

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

RFC status and corrections ↗