RFC 2817: Upgrading to TLS Within HTTP/1.1

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]

Read RFC 2817 on the RFC Editor

Outgoing relationships (7 related RFCs)

Updates, Informative reference — RFC 2616: Hypertext Transfer Protocol -- HTTP/1.1
Informative reference — RFC 2818: HTTP Over TLS
Informative reference — RFC 2246: The TLS Protocol Version 1.0
Informative reference — RFC 2396: Uniform Resource Identifiers (URI): Generic Syntax
Informative reference — RFC 2629: Writing I-Ds and RFCs using XML
Informative reference — RFC 2565: Internet Printing Protocol/1.0: Encoding and Transport
Informative reference — RFC 2518: HTTP Extensions for Distributed Authoring -- WEBDAV

Incoming relationships (16 related RFCs)

Updated by — RFC 7230: Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing
Updated by, Informatively referenced by — RFC 7231: Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content
Normatively referenced by — RFC 4825: The Extensible Markup Language (XML) Configuration Access Protocol (XCAP)
Normatively referenced by — RFC 5878: Transport Layer Security (TLS) Authorization Extensions
Normatively referenced by — RFC 6042: Transport Layer Security (TLS) Authorization Using KeyNote
Informatively referenced by — RFC 5056: On the Use of Channel Bindings to Secure Channels
Informatively referenced by — RFC 6454: The Web Origin Concept
Informatively referenced by — RFC 5988: Web Linking
Informatively referenced by — RFC 4217: Securing FTP with TLS
Informatively referenced by — RFC 9329: TCP Encapsulation of Internet Key Exchange Protocol (IKE) and IPsec Packets
Informatively referenced by — RFC 3914: Open Pluggable Edge Services (OPES) Treatment of IAB Considerations
Informatively referenced by — RFC 7605: Recommendations on Using Assigned Transport Port Numbers
Informatively referenced by — RFC 5970: DHCPv6 Options for Network Boot
Informatively referenced by — RFC 7472: Internet Printing Protocol (IPP) over HTTPS Transport Binding and the 'ipps' URI Scheme
Informatively referenced by — RFC 3507: Internet Content Adaptation Protocol (ICAP)
Informatively referenced by — RFC 9931: Security Considerations for Optimistic Protocol Transitions in HTTP/1.1