RFC 7231: Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content
0 sources
RFC 7231: Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content
Summary
RFC 7231: Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content is a Request for Comments[1].
Key Facts
- RFC 7231: Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content authored Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content — author (P50): Roy Fielding[2].
- RFC 7231: Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content authored Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content — author (P50): Julian Reschke[3].
- RFC 7231: Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content's instance of is recorded as Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content — instance of (P31): Request for Comments[4].
- RFC 7231: Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content's publisher is recorded as Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content — publisher (P123): Internet Engineering Task Force[5].
- RFC 7231: Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content's based on is recorded as Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content — based on (P144): RFC 2817: Upgrading to TLS Within HTTP/1.1[6].
- RFC 7231: Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content's DOI is recorded as 10.17487/RFC7231[7].
- RFC 7231: Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content's language of work or name is recorded as Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content — language of work or name (P407): English[8].
- RFC 7231: Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content's publication date is recorded as +2014-06-01T00:00:00Z[9].
- RFC 7231: Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content's RfC ID is recorded as 7231[10].
- RFC 7231: Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content's main subject is recorded as Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content — main subject (P921): HTTP/1.1[11].
- RFC 7231: Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content's work available at URL is recorded as https://tools.ietf.org/html/rfc7231[12].
- RFC 7231: Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content's work available at URL is recorded as https://tools.ietf.org/rfc/rfc7231.txt[13].
- RFC 7231: Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content's work available at URL is recorded as https://www.rfc-editor.org/rfc/rfc7231.txt[14].
- RFC 7231: Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content's work available at URL is recorded as https://www.rfc-editor.org/pdfrfc/rfc7231.txt.pdf[15].
- RFC 7231: Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content's number of pages is recorded as {'unit': '1', 'amount': '+101'}[16].
- RFC 7231: Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content's replaces is recorded as Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content — replaces (P1365): RFC 2616: Hypertext Transfer Protocol -- HTTP/1.1[17].
- RFC 7231: Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content's replaced by is recorded as Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content — replaced by (P1366): RFC 9110: HTTP Semantics[18].
- RFC 7231: Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content's title is recorded as Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content[19].
Body
Designation and Status
RFC 7231: Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content's instance of is recorded as Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content — instance of (P31): Request for Comments[4].