RFC 9110 / WEB FOUNDATIONS

One meaning, many transports

GET has a shared meaning whether an exchange uses HTTP/1.1, HTTP/2, or HTTP/3.

Related RFCs and changes

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

DIAGRAM§ 1.3 ↗

RFC 9110 · § 1.3EXAMPLE

3 / 3

Interpret the request.

The origin applies the shared method and field semantics.

Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references

WHAT CHANGED

RFC 7231 §3RFC 9110 §6

An abstract message model now describes components across HTTP versions, instead of tying the explanation to HTTP/1.1 syntax. Appendix B.3 documents this restructuring.

Read the updated RFC section ↗

KEY POINT

Separate what a message means from how it travels.

RFC 9110 defines semantics shared across HTTP versions.
RFCs 9112, 9113, and 9114 define version-specific communication.
A request identifies a target and desired action; its response reports the result.

DETAILS

This guide covers HTTP semantics. Moving from HTTP/2 to HTTP/3 changes the transport mapping, not the meaning of every method.

Read the RFC section ↗

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

Privacy

All chapters in this RFC