Establishing TLS over an existing HTTP connection
E835150
Establishing TLS over an existing HTTP connection is a technique that upgrades a plain HTTP session to a secure, encrypted TLS channel without creating a new TCP connection.
All labels observed (1)
| Label | Occurrences |
|---|---|
| Establishing TLS over an existing HTTP connection canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T10024777 — 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: Establishing TLS over an existing HTTP connection Context triple: [RFC 2817, definesMechanism, Establishing TLS over an existing HTTP connection]
-
A.
TLS-over-TCP
TLS-over-TCP is a secure communication method that encrypts data using the Transport Layer Security (TLS) protocol on top of the reliable Transmission Control Protocol (TCP).
-
B.
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.
-
C.
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.
-
D.
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.
-
E.
TLS
TLS (Transport Layer Security) is a cryptographic protocol that secures data transmitted over networks by providing encryption, authentication, and integrity between communicating applications.
- 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: Establishing TLS over an existing HTTP connection Target entity description: Establishing TLS over an existing HTTP connection is a technique that upgrades a plain HTTP session to a secure, encrypted TLS channel without creating a new TCP connection.
-
A.
TLS-over-TCP
TLS-over-TCP is a secure communication method that encrypts data using the Transport Layer Security (TLS) protocol on top of the reliable Transmission Control Protocol (TCP).
-
B.
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.
-
C.
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.
-
D.
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.
-
E.
TLS
TLS (Transport Layer Security) is a cryptographic protocol that secures data transmitted over networks by providing encryption, authentication, and integrity between communicating applications.
- F. None of above. chosen
Statements (48)
| Predicate | Object |
|---|---|
| instanceOf |
network protocol technique
ⓘ
security protocol upgrade mechanism ⓘ |
| affectedBy |
HTTP intermediaries and proxies
ⓘ
load balancers ⓘ middleboxes that inspect HTTP ⓘ |
| avoids | creating new TCP connection ⓘ |
| canBeUsedFor |
incremental security deployment
ⓘ
tunneling secure traffic through intermediaries ⓘ upgrading legacy HTTP services ⓘ |
| canImprove |
latency for protocol negotiation
ⓘ
performance by avoiding extra TCP handshake ⓘ |
| canUseMechanism |
HTTP Upgrade: TLS/1.0 header
ⓘ
HTTP Upgrade: TLS/1.2 header ⓘ HTTP Upgrade: h2c to h2 over TLS ⓘ |
| contrastsWith |
starting TLS at the beginning of TCP connection
ⓘ
using separate port for HTTPS ⓘ |
| hasChallenge |
compatibility with existing proxies
ⓘ
limited support in common HTTP clients ⓘ limited support in common HTTP servers ⓘ |
| hasGoal |
provide authentication
ⓘ
provide confidentiality ⓘ provide integrity ⓘ upgrade plain HTTP to encrypted channel ⓘ |
| hasProperty |
in-band negotiation
ⓘ
no change of client IP or port ⓘ no change of server IP or port ⓘ session continuity at application level ⓘ |
| hasSecurityConsideration |
downgrade attack risk if negotiation is not authenticated
ⓘ
need to validate TLS certificates after upgrade ⓘ plaintext data sent before upgrade remains unprotected ⓘ |
| isConceptuallySimilarTo |
STARTTLS in IMAP
NERFINISHED
ⓘ
STARTTLS in POP3 NERFINISHED ⓘ STARTTLS in SMTP NERFINISHED ⓘ |
| isPartOf | secure web communication techniques ⓘ |
| mayBeSpecifiedIn | experimental or proprietary HTTP extensions ⓘ |
| mayRequire |
HTTP 101 Switching Protocols response
ⓘ
HTTP 200 response before TLS negotiation in some designs ⓘ |
| operatesOnLayer | application layer ⓘ |
| relatedTo |
HTTP CONNECT method
NERFINISHED
ⓘ
HTTP Upgrade header ⓘ HTTP/2 prior knowledge upgrade ⓘ STARTTLS NERFINISHED ⓘ WebSocket protocol upgrade ⓘ |
| requires |
client support
ⓘ
server support ⓘ |
| reuses | existing TCP connection ⓘ |
| usesProtocol |
Hypertext Transfer Protocol
NERFINISHED
ⓘ
Transport Layer Security NERFINISHED ⓘ |
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: Establishing TLS over an existing HTTP connection Description of subject: Establishing TLS over an existing HTTP connection is a technique that upgrades a plain HTTP session to a secure, encrypted TLS channel without creating a new TCP connection.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.