RFC 2817: Upgrading to TLS Within HTTP/1.1
In plain English — editorial summary, not part of the RFC
This memo explains how to use the Upgrade mechanism in HTTP/1.1 to initiate Transport Layer Security (TLS) over an existing TCP connection. [STANDARDS-TRACK]
Document record
- Document ID
- RFC2817
- Published
- May 2000
- Authors
- R. Khare; S. Lawrence
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 13
- Also known as
- —
- Updates:
- RFC 2616
Topics
Referenced by
2 later RFCs formally update or obsolete part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2712Addition of Kerberos Cipher Suites to Transport Layer Security (TLS)Current
October 1999
- RFC 2585Internet X.509 Public Key Infrastructure Operational Protocols: FTP and HTTPCurrent
May 1999
- RFC 3268Advanced Encryption Standard (AES) Ciphersuites for Transport Layer Security (TLS)Obsoleted
July 2002
- RFC 3546Transport Layer Security (TLS) ExtensionsObsoleted
June 2003
- RFC 3749Transport Layer Security Protocol Compression MethodsUpdated
May 2004
- RFC 6331Moving DIGEST-MD5 to HistoricCurrent
July 2011
- RFC 7457Summarizing Known Attacks on Transport Layer Security (TLS) and Datagram TLS (DTLS)Current
February 2015
- RFC 7465Prohibiting RC4 Cipher SuitesUpdated
February 2015
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?