RFC 2817
E200697
RFC 2817 is an Internet standard that specifies how to use the HTTP/1.1 Upgrade mechanism to establish Transport Layer Security (TLS) over an existing HTTP connection.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 2817 canonical | 1 |
Statements (47)
| Predicate | Object |
|---|---|
| instanceOf |
Internet standard
ⓘ
Request for Comments ⓘ |
| alternativeTo | Using a separate port for HTTPS such as 443 ⓘ |
| area | Applications Area ⓘ |
| category | Standards Track ⓘ |
| definesClientBehavior | How an HTTP client requests TLS upgrade using Upgrade header ⓘ |
| definesInteraction |
Client-initiated protocol switch from HTTP to TLS
ⓘ
Server acceptance or rejection of TLS upgrade ⓘ |
| definesMechanism |
Establishing TLS over an existing HTTP connection
ⓘ
In-band upgrade from cleartext HTTP to TLS ⓘ Use of HTTP/1.1 Upgrade header to initiate TLS ⓘ |
| definesRequirementLevel | Implementation considerations for HTTP clients and servers supporting Upgrade to TLS ⓘ |
| definesServerBehavior | How an HTTP server responds to TLS upgrade requests ⓘ |
| definesStatusCodeUsage | 101 Switching Protocols ⓘ |
| definesTerm | TLS upgrade ⓘ |
| definesUseCase |
Securing HTTP traffic without changing the initial port
ⓘ
Upgrading a persistent HTTP connection to TLS ⓘ |
| documentType | Technical specification ⓘ |
| focusesOn | Transition from non-encrypted to encrypted HTTP on the same connection ⓘ |
| intendedUse |
Environments where port sharing between HTTP and HTTPS is desired
ⓘ
Scenarios requiring dynamic negotiation of TLS ⓘ |
| language | English ⓘ |
| obsoletedBy |
Later HTTP/HTTPS deployment practices favoring separate ports
ⓘ
RFC 7230 (indirectly, via HTTP/1.1 revision) ⓘ |
| obsoletes | RFC 2817 (Proposed Drafts or earlier versions) ⓘ |
| portUsage | Allows TLS over the same port as cleartext HTTP ⓘ |
| protocol |
HTTP
ⓘ
surface form:
Hypertext Transfer Protocol
|
| protocolVersion | HTTP/1.1 ⓘ |
| publishedBy |
Internet Engineering Task Force
ⓘ
surface form:
IETF
Internet Engineering Task Force ⓘ |
| publisher | RFC Editor ⓘ |
| relatedTo |
HTTP Upgrade mechanism
ⓘ
HTTPS ⓘ RFC 2616 ⓘ |
| relatedWorkingGroup | HTTP Working Group ⓘ |
| RFCNumber | 2817 ⓘ |
| scope | Application-layer security negotiation for HTTP ⓘ |
| securityProtocol |
TLS
ⓘ
TLS ⓘ
surface form:
Transport Layer Security
|
| series |
RFCs
ⓘ
surface form:
STD (Standards Track RFCs)
|
| standardsStatus | Proposed Standard ⓘ |
| statusAsOf2024 | Historic ⓘ |
| title | Upgrading to TLS Within HTTP/1.1 ⓘ |
| updatesProtocol | HTTP/1.1 ⓘ |
| usesHeaderField |
101 Switching Protocols status code
ⓘ
Connection ⓘ Upgrade ⓘ |
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.