Encryption and peer identity
TLS protects communication against eavesdropping and tampering. During a TLS 1.3 handshake, peers negotiate relevant parameters and establish traffic keys. Encryption alone is insufficient if the endpoint has established those keys with an unintended peer.
An ordinary HTTPS client validates certificate trust, validity and the requested server name, among other requirements. Unconditionally accepting a self-signed certificate can retain encrypted traffic while removing a meaningful identity check. Distinguish possession of a certificate file from successful validation under the client’s trust policy.
Certificates and traffic keys
Do not picture every application byte as directly encrypted with the public key written in the server certificate. Authentication in the handshake and the symmetric keys used to protect traffic records have different roles. Key agreement, signatures and record encryption should be explained separately.
For example, reaching an IP address does not establish that a certificate authenticates the requested website. A name mismatch can invalidate the intended HTTPS connection even though a transport connection exists. Keep address resolution separate from the hostname whose identity the client is checking.
Early data and replay
Session resumption can support 0-RTT early data, reducing a handshake delay before some application data is sent. That benefit comes with replay considerations. The application must decide what happens if an early request is accepted more than once.
A purchase operation is not automatically safe simply because its bytes are encrypted. Confidentiality and exactly-once business execution are different properties. Restrict early data to suitable operations and use application-level safeguards where needed. Do not treat connection resumption as permission to replay arbitrary state-changing requests.
What TLS does not protect
TLS protects a communication segment, not every later use of the data. It cannot automatically prevent incorrect server-side authorization or secrets written to logs. If a CDN terminates TLS, evaluate subsequent connections and processing as separate parts of the trust boundary.
When diagnosing failures, separate transport reachability, handshake negotiation, certificate validation and HTTP behavior. Find the mismatch in clocks, certificate chains or names rather than disabling validation to hide the symptom. A successful TLS handshake also does not imply that the user is authorized for a particular application resource.