Upgrading to TLS Within HTTP/1.1
E835149
"Upgrading to TLS Within HTTP/1.1" is an IETF standards-track specification that defines how HTTP/1.1 connections can be dynamically upgraded from cleartext to Transport Layer Security (TLS) using the HTTP Upgrade mechanism.
All labels observed (2)
| Label | Occurrences |
|---|---|
| Upgrading to TLS Within HTTP/1.1 canonical | 2 |
| RFC 2616 TLS upgrade approach | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T10024766 — resolving that mention is where its identity was fixed. The disambiguator weighed these candidate entities and picked the highlighted one (or “None”, minting a new entity). This is how homonymy is resolved: the same surface form can point to different entities.
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Upgrading to TLS Within HTTP/1.1 Context triple: [RFC 2817, title, Upgrading to TLS Within HTTP/1.1]
-
A.
Deprecating TLS 1.0 and TLS 1.1
"Deprecating TLS 1.0 and TLS 1.1" is an IETF standards-track document that formally declares the older TLS 1.0 and 1.1 protocol versions obsolete and recommends their removal from use in favor of more secure versions like TLS 1.2 and 1.3.
-
B.
TLS 1.2
TLS 1.2 is a widely deployed version of the Transport Layer Security protocol that provides encrypted and authenticated communication over computer networks.
-
C.
UTA (Using TLS in Applications)
UTA (Using TLS in Applications) is an IETF working group focused on defining best practices and standards for the secure use of Transport Layer Security (TLS) in application protocols.
-
D.
TLS 1.1
TLS 1.1 is an older version of the Transport Layer Security protocol that improved upon earlier SSL standards but has since been deprecated in favor of more secure versions like TLS 1.2 and 1.3.
-
E.
AT-TLS (Application Transparent TLS)
AT-TLS (Application Transparent TLS) is an IBM z/OS networking function that transparently provides TLS encryption and decryption for application traffic without requiring changes to the applications themselves.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Upgrading to TLS Within HTTP/1.1 Target entity description: "Upgrading to TLS Within HTTP/1.1" is an IETF standards-track specification that defines how HTTP/1.1 connections can be dynamically upgraded from cleartext to Transport Layer Security (TLS) using the HTTP Upgrade mechanism.
-
A.
Deprecating TLS 1.0 and TLS 1.1
"Deprecating TLS 1.0 and TLS 1.1" is an IETF standards-track document that formally declares the older TLS 1.0 and 1.1 protocol versions obsolete and recommends their removal from use in favor of more secure versions like TLS 1.2 and 1.3.
-
B.
TLS 1.2
TLS 1.2 is a widely deployed version of the Transport Layer Security protocol that provides encrypted and authenticated communication over computer networks.
-
C.
UTA (Using TLS in Applications)
UTA (Using TLS in Applications) is an IETF working group focused on defining best practices and standards for the secure use of Transport Layer Security (TLS) in application protocols.
-
D.
TLS 1.1
TLS 1.1 is an older version of the Transport Layer Security protocol that improved upon earlier SSL standards but has since been deprecated in favor of more secure versions like TLS 1.2 and 1.3.
-
E.
AT-TLS (Application Transparent TLS)
AT-TLS (Application Transparent TLS) is an IBM z/OS networking function that transparently provides TLS encryption and decryption for application traffic without requiring changes to the applications themselves.
- F. None of above. chosen
Statements (42)
| Predicate | Object |
|---|---|
| instanceOf |
HTTP protocol extension
ⓘ
IETF standards-track specification ⓘ RFC ⓘ |
| abbreviation | TLS ⓘ |
| appliesTo |
HTTP origin servers
ⓘ
HTTP proxies ⓘ HTTP user agents ⓘ |
| area | Applications ⓘ |
| category | Standards Track ⓘ |
| defines | use of the Upgrade header field value "TLS/1.0" and later ⓘ |
| definesClientBehavior | requesting TLS upgrade over an existing HTTP/1.1 connection ⓘ |
| definesHeaderField |
Connection
ⓘ
Upgrade ⓘ |
| definesMechanismFor | upgrading HTTP/1.1 connections to TLS ⓘ |
| definesServerBehavior | accepting or rejecting TLS upgrade requests ⓘ |
| definesStatusCodeUsage | 101 Switching Protocols ⓘ |
| definesTerm | TLS upgrade for HTTP/1.1 ⓘ |
| ensures |
confidentiality after TLS upgrade
ⓘ
integrity after TLS upgrade ⓘ server authentication after TLS upgrade ⓘ |
| goal | enable dynamic transition from cleartext HTTP to TLS ⓘ |
| intendedFor |
HTTP implementers
ⓘ
security protocol implementers ⓘ |
| obsoletes |
RFC 2616 TLS upgrade approach
ⓘ
linked to:
Upgrading to TLS Within HTTP/1.1
|
| partOfSeries |
Request for Comments
ⓘ
linked to:
RFCs
|
| protocolVersion | HTTP/1.1 ⓘ |
| publishedBy |
IETF
ⓘ
linked to:
Internet Engineering Task Force
Internet Engineering Task Force ⓘ |
| relatedTo |
HTTP Upgrade mechanism
ⓘ
HTTP/1.1 ⓘ Transport Layer Security ⓘ
linked to:
TLS
|
| RFCNumber | 2817 ⓘ |
| securityProtocol |
Transport Layer Security
ⓘ
linked to:
TLS
|
| specifies |
interaction between HTTP status codes and protocol switching
ⓘ
requirements for intermediaries handling TLS upgrades ⓘ |
| standardsBody |
IETF Applications Area
ⓘ
linked to:
IETF Areas
|
| status | Internet Standard track document ⓘ |
| supportsUseCase | starting in cleartext HTTP and upgrading to TLS on the same TCP connection ⓘ |
| title | Upgrading to TLS Within HTTP/1.1 ⓘ |
| transportLayer |
TCP
ⓘ
linked to:
Transmission Control Protocol
|
| updates | HTTP/1.1 usage with TLS ⓘ |
| usesMechanism | HTTP Upgrade header ⓘ |
How these facts were elicited
The pipeline generated the facts above by prompting gpt-5.1 with this entity's name + description and the instruction below.
Instruction
You are a knowledge base construction expert. Given a subject entity and a description of it, return factual statements that you know for the subject as a JSON list of dictionaries(triples), where keys must be "subject", "predicate" and "object". The number of facts may be very high, between 25 to 50 or more, for very popular subjects. For less popular subjects, the number of facts can be very low, like 5 or 10. # Requirements - If you don't know the subject at all, return an empty list. - If the subject is not a named entity, return an empty list. - Include at least one triple where predicate is "instanceOf". - Do not get too wordy. - Separate several objects into multiple triples with one object.
Input
Subject: Upgrading to TLS Within HTTP/1.1 Description of subject: "Upgrading to TLS Within HTTP/1.1" is an IETF standards-track specification that defines how HTTP/1.1 connections can be dynamically upgraded from cleartext to Transport Layer Security (TLS) using the HTTP Upgrade mechanism.
Referenced by (3)
Full triples — surface form annotated when it differs from this entity's canonical label.
linked to: Upgrading to TLS Within HTTP/1.1