bk99.de entertain the web since 1997

bk99.de
RFC · WebStandard explained

RFC 9110: HTTP semantics reorganised

Summary

RFC 9110 defines the shared semantics of HTTP independently of the concrete transport versions. Separate semantics allow HTTP/1.1, HTTP/2 and HTTP/3 to share a common basis. Clear terms reduce contradictory implementations.

Ideas

  • Methods describe intended operations.
  • Status codes carry the same meaning across protocol versions.
  • Field definitions explain caching and forwarding.

Facts

  • RFC 9110 replaces RFC 2818.

Remarks

  • RFC 9110 has the status “Internet Standard”; current errata and successor documents should also be checked.

Recommendations

  • Use RFC 9110 instead of the superseded monolithic HTTP specifications.
  • Separate application semantics from transport optimisation.

References

Read the RFC at the RFC Editor

Search the Web Archive

RFC · 2026

RFC 10008: HTTP QUERY: Safe, idempotent queries with content

RFC 10008 defines the HTTP method QUERY for complex, safe and idempotent queries with request content. New methods close gaps when established semantics do not fit cleanly. Explicit semantics are better than misused POST requests.

RFC · 2022

RFC 9114: HTTP/3 over QUIC

RFC 9114 maps HTTP semantics onto QUIC and avoids TCP-induced blocking between independent streams. HTTP/3 ties application and transport development more closely together than earlier versions. UDP reachability becomes an important operational factor again.

RFC · 2016

RFC 7725: HTTP 451: Unavailable for legal reasons

RFC 7725 defines status code 451 for resources to which access is denied because of legal demands. Error codes can make social causes technically visible. Transparency about blocking is itself part of an open network infrastructure.