HTTP Semantics
Embed This Widget
Add the script tag and a data attribute to embed this widget.
Embed via iframe for maximum compatibility.
<iframe src="https://ipfyi.com/iframe/entity//" width="420" height="400" frameborder="0" style="border:0;border-radius:10px;max-width:100%" loading="lazy"></iframe>Paste this URL in WordPress, Medium, or any oEmbed-compatible platform.
https://ipfyi.com/entity//Add a dynamic SVG badge to your README or docs.
[](https://ipfyi.com/entity//)Use the native HTML custom element.
R. Fielding, M. Nottingham, J. Reschke · 2022-06
Abstract
RFC 9110 defines the semantics of the Hypertext Transfer Protocol (HTTP), covering the core concepts that apply across all HTTP versions: methods (GET, POST, PUT, DELETE, etc.), status codes, header fields, content negotiation, authentication, and caching. It separates protocol semantics from the version-specific syntax and framing defined in RFC 9112 (HTTP/1.1), RFC 9113 (HTTP/2), and RFC 9114 (HTTP/3).
Why This RFC Matters
RFC 9110 is the authoritative reference for HTTP semantics as of 2022, consolidating and superseding the RFC 7230–7235 series and the original RFC 2616. Its separation of semantics from version-specific framing was a deliberate architectural decision: HTTP/1.1, HTTP/2, and HTTP/3 share the same methods, status codes, and header semantics, differing only in how messages are encoded on the wire. This document defines what every web developer must understand — the meaning of a 301 redirect, the semantics of a GET request, or the rules for cache validation — independent of which HTTP version is in use.