RFC 7234: Hypertext Transfer Protocol (HTTP/1.1): Caching
request for comments publication
Press Enter · cited answer in seconds
0 sources
RFC 7234: Hypertext Transfer Protocol (HTTP/1.1): Caching
Summary
RFC 7234: Hypertext Transfer Protocol (HTTP/1.1): Caching is a Request for Comments[1].
Key Facts
- RFC 7234: Hypertext Transfer Protocol (HTTP/1.1): Caching authored Hypertext Transfer Protocol (HTTP/1.1): Caching — author (P50): Roy Fielding[2].
- RFC 7234: Hypertext Transfer Protocol (HTTP/1.1): Caching authored Hypertext Transfer Protocol (HTTP/1.1): Caching — author (P50): Julian Reschke[3].
- RFC 7234: Hypertext Transfer Protocol (HTTP/1.1): Caching authored Hypertext Transfer Protocol (HTTP/1.1): Caching — author (P50): Mark Nottingham[4].
- RFC 7234: Hypertext Transfer Protocol (HTTP/1.1): Caching's instance of is recorded as Hypertext Transfer Protocol (HTTP/1.1): Caching — instance of (P31): Request for Comments[5].
- RFC 7234: Hypertext Transfer Protocol (HTTP/1.1): Caching's publisher is recorded as Hypertext Transfer Protocol (HTTP/1.1): Caching — publisher (P123): Internet Engineering Task Force[6].
- RFC 7234: Hypertext Transfer Protocol (HTTP/1.1): Caching's DOI is recorded as 10.17487/RFC7234[7].
- RFC 7234: Hypertext Transfer Protocol (HTTP/1.1): Caching's language of work or name is recorded as Hypertext Transfer Protocol (HTTP/1.1): Caching — language of work or name (P407): English[8].
- RFC 7234: Hypertext Transfer Protocol (HTTP/1.1): Caching's publication date is recorded as +2014-06-01T00:00:00Z[9].
- RFC 7234: Hypertext Transfer Protocol (HTTP/1.1): Caching's RfC ID is recorded as 7234[10].
- RFC 7234: Hypertext Transfer Protocol (HTTP/1.1): Caching's main subject is recorded as Hypertext Transfer Protocol (HTTP/1.1): Caching — main subject (P921): HTTP/1.1[11].
- RFC 7234: Hypertext Transfer Protocol (HTTP/1.1): Caching's main subject is recorded as Hypertext Transfer Protocol (HTTP/1.1): Caching — main subject (P921): HTTP Caching[12].
- RFC 7234: Hypertext Transfer Protocol (HTTP/1.1): Caching's work available at URL is recorded as https://tools.ietf.org/html/rfc7234[13].
- RFC 7234: Hypertext Transfer Protocol (HTTP/1.1): Caching's work available at URL is recorded as https://tools.ietf.org/rfc/rfc7234.txt[14].
- RFC 7234: Hypertext Transfer Protocol (HTTP/1.1): Caching's work available at URL is recorded as https://www.rfc-editor.org/rfc/rfc7234.txt[15].
- RFC 7234: Hypertext Transfer Protocol (HTTP/1.1): Caching's work available at URL is recorded as https://www.rfc-editor.org/pdfrfc/rfc7234.txt.pdf[16].
- RFC 7234: Hypertext Transfer Protocol (HTTP/1.1): Caching's number of pages is recorded as {'unit': '1', 'amount': '+43'}[17].
- RFC 7234: Hypertext Transfer Protocol (HTTP/1.1): Caching's replaces is recorded as Hypertext Transfer Protocol (HTTP/1.1): Caching — replaces (P1365): RFC 2616: Hypertext Transfer Protocol -- HTTP/1.1[18].
- RFC 7234: Hypertext Transfer Protocol (HTTP/1.1): Caching's replaced by is recorded as Hypertext Transfer Protocol (HTTP/1.1): Caching — replaced by (P1366): RFC 9111: HTTP Caching[19].
- RFC 7234: Hypertext Transfer Protocol (HTTP/1.1): Caching's title is recorded as Hypertext Transfer Protocol (HTTP/1.1): Caching[20].
- RFC 7234: Hypertext Transfer Protocol (HTTP/1.1): Caching's DBLP publication ID is recorded as journals/rfc/rfc7234[21].
Body
Designation and Status
RFC 7234: Hypertext Transfer Protocol (HTTP/1.1): Caching's instance of is recorded as Hypertext Transfer Protocol (HTTP/1.1): Caching — instance of (P31): Request for Comments[5].