Home › Entities › request_for_comments › RFC 2817: Upgrading to TLS Within HTTP/1.1

RFC 2817: Upgrading to TLS Within HTTP/1.1

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

RFC 2817: Upgrading to TLS Within HTTP/1.1

Summary

RFC 2817: Upgrading to TLS Within HTTP/1.1 is a Request for Comments[1].

Key Facts

  • RFC 2817: Upgrading to TLS Within HTTP/1.1's instance of is recorded as Upgrading to TLS Within HTTP/1.1 — instance of (P31): Request for Comments[2].
  • RFC 2817: Upgrading to TLS Within HTTP/1.1's publisher is recorded as Upgrading to TLS Within HTTP/1.1 — publisher (P123): Internet Engineering Task Force[3].
  • RFC 2817: Upgrading to TLS Within HTTP/1.1's based on is recorded as Upgrading to TLS Within HTTP/1.1 — based on (P144): RFC 2616: Hypertext Transfer Protocol -- HTTP/1.1[4].
  • RFC 2817: Upgrading to TLS Within HTTP/1.1's DOI is recorded as 10.17487/RFC2817[5].
  • RFC 2817: Upgrading to TLS Within HTTP/1.1's language of work or name is recorded as Upgrading to TLS Within HTTP/1.1 — language of work or name (P407): English[6].
  • RFC 2817: Upgrading to TLS Within HTTP/1.1's publication date is recorded as +2000-05-01T00:00:00Z[7].
  • RFC 2817: Upgrading to TLS Within HTTP/1.1's RfC ID is recorded as 2817[8].
  • RFC 2817: Upgrading to TLS Within HTTP/1.1's main subject is recorded as Upgrading to TLS Within HTTP/1.1 — main subject (P921): HTTPS[9].
  • RFC 2817: Upgrading to TLS Within HTTP/1.1's work available at URL is recorded as https://tools.ietf.org/html/rfc2817[10].
  • RFC 2817: Upgrading to TLS Within HTTP/1.1's work available at URL is recorded as https://tools.ietf.org/rfc/rfc2817.txt[11].
  • RFC 2817: Upgrading to TLS Within HTTP/1.1's work available at URL is recorded as https://www.rfc-editor.org/rfc/rfc2817.txt[12].
  • RFC 2817: Upgrading to TLS Within HTTP/1.1's work available at URL is recorded as https://www.rfc-editor.org/pdfrfc/rfc2817.txt.pdf[13].
  • RFC 2817: Upgrading to TLS Within HTTP/1.1's number of pages is recorded as {'unit': '1', 'amount': '+13'}[14].
  • RFC 2817: Upgrading to TLS Within HTTP/1.1's title is recorded as Upgrading to TLS Within HTTP/1.1[15].
  • RFC 2817: Upgrading to TLS Within HTTP/1.1's author name string is recorded as R. Khare[16].
  • RFC 2817: Upgrading to TLS Within HTTP/1.1's author name string is recorded as S. Lawrence[17].
  • RFC 2817: Upgrading to TLS Within HTTP/1.1's amended by is recorded as Upgrading to TLS Within HTTP/1.1 — amended by (P2567): RFC 7230: Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing[18].
  • RFC 2817: Upgrading to TLS Within HTTP/1.1's amended by is recorded as Upgrading to TLS Within HTTP/1.1 — amended by (P2567): RFC 7231: Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content[19].
  • RFC 2817: Upgrading to TLS Within HTTP/1.1's DBLP publication ID is recorded as journals/rfc/rfc2817[20].

Body

Designation and Status

RFC 2817: Upgrading to TLS Within HTTP/1.1's instance of is recorded as Upgrading to TLS Within HTTP/1.1 — instance of (P31): Request for Comments[2].

References

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

Direct Wikidata claims

  1. [2] ↑ . RFC Index. Retrieved . wikidata.org.
  2. [3] ↑ . RFC Index. Retrieved . wikidata.org.
  3. [4] ↑ . RFC Index. Retrieved . 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] ↑ . wikidata.org.
  9. [10] ↑ . RFC Index. Retrieved . wikidata.org.
  10. [11] ↑ . RFC Index. Retrieved . wikidata.org.
  11. [12] ↑ . RFC Index. Retrieved . wikidata.org.
  12. [13] ↑ . RFC Index. Retrieved . wikidata.org.
  13. [14] ↑ . RFC Index. Retrieved . wikidata.org.
  14. [15] ↑ . RFC Index. 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] ↑ . DBLP Dataset 2021-01-02. 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 2817: Upgrading to TLS Within HTTP/1.1. Retrieved May 3, 2026, from https://4ort.xyz/entity/rfc-2817-upgrading-to-tls-within-http-1-1
MLA “RFC 2817: Upgrading to TLS Within HTTP/1.1.” 4ort.xyz Knowledge Graph, 4ort.xyz, 3 May. 2026, https://4ort.xyz/entity/rfc-2817-upgrading-to-tls-within-http-1-1.
BibTeX @misc{4ortxyz_rfc-2817-upgrading-to-tls-within-http-1-1_2026, author = {{4ort.xyz Knowledge Graph}}, title = {{RFC 2817: Upgrading to TLS Within HTTP/1.1}}, year = {2026}, url = {https://4ort.xyz/entity/rfc-2817-upgrading-to-tls-within-http-1-1}, note = {Accessed: 2026-05-03}}
LLM prompt According to 4ort.xyz Knowledge Graph (aggregator of Wikidata, Wikipedia, and authoritative open-data sources): RFC 2817: Upgrading to TLS Within HTTP/1.1 — https://4ort.xyz/entity/rfc-2817-upgrading-to-tls-within-http-1-1 (retrieved 2026-05-03)

Canonical URL: https://4ort.xyz/entity/rfc-2817-upgrading-to-tls-within-http-1-1 · Last refreshed: