HTTP Semantics

Fielding, R. T., Nottingham, Mark, & Reschke, J. (2022). HTTP Semantics.

Type

Report

Intellectual base

Grey literature

Year

2022

DOI

10.17487/rfc9110

Link

https://doi.org/10.17487/RFC9110

Cited by

3 citations across 3 artifacts.

Each citation links to the sentence it supports in the citing article.

Domain-specific

• Request-Response
  • HTTP instantiates the pattern in its canonical form: a client sends a method-plus-URI request with optional headers and body; a server returns a status code, headers, and optional body; the TCP connection or an explicit request identifier correlates them.

    This sourceThe current HTTP specification, defining the request as method-plus-target-URI with optional header fields and content, the response as status code plus header fields and content, and correlation as version-dependent - implicit message ordering on a connection, or an explicit identifier.

• URL Redirection
  • RFC 9110 distinguishes permanent from temporary redirects and method-changing from method-preserving behavior; it also warns clients to intervene in cycles and to reconsider sensitive headers when the origin changes.

Mechanisms

• Maintenance Mode
  • So operations declares maintenance mode: the app returns an HTTP 503 "Service Unavailable"

    This sourceDefines HTTP 503 as Service Unavailable and permits Retry-After to indicate the expected period of unavailability.

Verification

This reference passed the adversarial substantiation pipeline: it was checked to exist and to support the claim it is attached to. See how references were verified.

Links previously used in the corpus

Before the registry existed this work was also linked 1 other way.

• https://www.rfc-editor.org/rfc/rfc9110.html#section-15.4 ×1

Registry ID ref:e5a130fb89c6 · see in the full table