Home › Entities › request_for_comments › RFC 9110: HTTP Semantics

RFC 9110: HTTP Semantics

request for comments publication
Place request_for_comments Q112263672
Press Enter · cited answer in seconds

RFC 9110: HTTP Semantics

Summary

RFC 9110: HTTP Semantics is a Request for Comments[1].

Key Facts

  • RFC 9110: HTTP Semantics authored HTTP Semantics — author (P50): Julian Reschke[2].
  • RFC 9110: HTTP Semantics authored HTTP Semantics — author (P50): Roy Fielding[3].
  • RFC 9110: HTTP Semantics's instance of is recorded as HTTP Semantics — instance of (P31): Request for Comments[4].
  • RFC 9110: HTTP Semantics's publisher is recorded as HTTP Semantics — publisher (P123): Internet Engineering Task Force[5].
  • RFC 9110: HTTP Semantics's based on is recorded as HTTP Semantics — based on (P144): RFC 3864: Registration Procedures for Message Header Fields[6].
  • RFC 9110: HTTP Semantics's DOI is recorded as 10.17487/RFC9110[7].
  • RFC 9110: HTTP Semantics's language of work or name is recorded as HTTP Semantics — language of work or name (P407): English[8].
  • RFC 9110: HTTP Semantics's publication date is recorded as +2022-06-00T00:00:00Z[9].
  • RFC 9110: HTTP Semantics's RfC ID is recorded as 9110[10].
  • RFC 9110: HTTP Semantics's main subject is recorded as HTTP Semantics — main subject (P921): HTTP[11].
  • RFC 9110: HTTP Semantics's work available at URL is recorded as https://www.rfc-editor.org/rfc/rfc9110.html[12].
  • RFC 9110: HTTP Semantics's work available at URL is recorded as https://www.rfc-editor.org/rfc/rfc9110.pdf[13].
  • RFC 9110: HTTP Semantics's work available at URL is recorded as https://tools.ietf.org/html/rfc9110[14].
  • RFC 9110: HTTP Semantics's number of pages is recorded as {'unit': '1', 'amount': '+252'}[15].
  • RFC 9110: HTTP Semantics's replaces is recorded as HTTP Semantics — replaces (P1365): RFC 2818: HTTP Over TLS[16].
  • RFC 9110: HTTP Semantics's replaces is recorded as HTTP Semantics — replaces (P1365): RFC 7230: Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing[17].
  • RFC 9110: HTTP Semantics's replaces is recorded as HTTP Semantics — replaces (P1365): RFC 7231: Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content[18].
  • RFC 9110: HTTP Semantics's replaces is recorded as HTTP Semantics — replaces (P1365): RFC 7232: Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests[19].
  • RFC 9110: HTTP Semantics's replaces is recorded as HTTP Semantics — replaces (P1365): RFC 7233: Hypertext Transfer Protocol (HTTP/1.1): Range Requests[20].
  • RFC 9110: HTTP Semantics's replaces is recorded as HTTP Semantics — replaces (P1365): RFC 7235: Hypertext Transfer Protocol (HTTP/1.1): Authentication[21].
  • RFC 9110: HTTP Semantics's replaces is recorded as HTTP Semantics — replaces (P1365): RFC 7538: The Hypertext Transfer Protocol Status Code 308 (Permanent Redirect)[22].
  • RFC 9110: HTTP Semantics's replaces is recorded as HTTP Semantics — replaces (P1365): RFC 7615: HTTP Authentication-Info and Proxy-Authentication-Info Response Header Fields[23].
  • RFC 9110: HTTP Semantics's replaces is recorded as HTTP Semantics — replaces (P1365): RFC 7694: Hypertext Transfer Protocol (HTTP) Client-Initiated Content-Encoding[24].
  • RFC 9110: HTTP Semantics's title is recorded as HTTP Semantics[25].
  • RFC 9110: HTTP Semantics's author name string is recorded as M. Nottingham[26].

Body

Designation and Status

RFC 9110: HTTP Semantics's instance of is recorded as HTTP Semantics — instance of (P31): Request for Comments[4].

References

Programmatic citations — every numbered marker resolves to a verifiable graph row below.

Direct Wikidata claims

  1. [4] ↑ . RFC Index. Retrieved . wikidata.org.
  2. [2] ↑ . wikidata.org.
  3. [3] ↑ . wikidata.org.
  4. [5] ↑ . RFC Index. Retrieved . wikidata.org.
  5. [6] ↑ . RFC Index. Retrieved . wikidata.org.
  6. [7] ↑ . RFC Index. Retrieved . wikidata.org.
  7. [8] ↑ . RFC Index. Retrieved . wikidata.org.
  8. [9] ↑ . RFC Index. Retrieved . wikidata.org.
  9. [10] ↑ . RFC Index. Retrieved . wikidata.org.
  10. [11] ↑ . wikidata.org.
  11. [12] ↑ . wikidata.org.
  12. [13] ↑ . wikidata.org.
  13. [14] ↑ . RFC Index. Retrieved . wikidata.org.
  14. [15] ↑ . RFC 9110: HTTP Semantics. Retrieved . wikidata.org.
  15. [16] ↑ . RFC Index. Retrieved . wikidata.org.
  16. [17] ↑ . RFC Index. Retrieved . wikidata.org.
  17. [18] ↑ . RFC Index. Retrieved . wikidata.org.
  18. [19] ↑ . RFC Index. Retrieved . wikidata.org.
  19. [20] ↑ . RFC Index. Retrieved . wikidata.org.
  20. [21] ↑ . RFC Index. Retrieved . wikidata.org.
  21. [22] ↑ . RFC Index. Retrieved . wikidata.org.
  22. [23] ↑ . RFC Index. Retrieved . wikidata.org.
  23. [24] ↑ . RFC Index. Retrieved . wikidata.org.
  24. [25] ↑ . RFC Index. Retrieved . wikidata.org.
  25. [26] ↑ . RFC Index. Retrieved . wikidata.org.

Class ancestry

  1. [1] ↑ . Wikidata. wikidata.org.

📑 Cite this page

Use these citations when quoting this entity in research, articles, AI prompts, or wherever provenance matters. We aggregate Wikidata + Wikipedia + authoritative open-data sources; the stitched, scored, cross-referenced view is what 4ort.xyz contributes.

APA 4ort.xyz Knowledge Graph. (2026). RFC 9110: HTTP Semantics. Retrieved May 3, 2026, from https://4ort.xyz/entity/rfc-9110-http-semantics
MLA “RFC 9110: HTTP Semantics.” 4ort.xyz Knowledge Graph, 4ort.xyz, 3 May. 2026, https://4ort.xyz/entity/rfc-9110-http-semantics.
BibTeX @misc{4ortxyz_rfc-9110-http-semantics_2026, author = {{4ort.xyz Knowledge Graph}}, title = {{RFC 9110: HTTP Semantics}}, year = {2026}, url = {https://4ort.xyz/entity/rfc-9110-http-semantics}, note = {Accessed: 2026-05-03}}
LLM prompt According to 4ort.xyz Knowledge Graph (aggregator of Wikidata, Wikipedia, and authoritative open-data sources): RFC 9110: HTTP Semantics — https://4ort.xyz/entity/rfc-9110-http-semantics (retrieved 2026-05-03)

Canonical URL: https://4ort.xyz/entity/rfc-9110-http-semantics · Last refreshed: