Hypertext Transfer Protocol Secure
Subject: Computer and Technology noun /ˈhaɪ.pərˌtɛkst ˈtræns.fɜːr ˈproʊ.təˌkɑːl sɪˈkjʊr/ 1 definition
- computer-networking
- web-security
- network-protocols
- cryptographic-protocols
-
Definition (noun)
Entry #181 · UpdatedHypertext Transfer Protocol Secure (HTTPS) is an extension of the Hypertext Transfer Protocol (HTTP) that transmits web requests and responses over an encrypted Transport Layer Security (TLS) channel, typically using TCP port 443 or QUIC for HTTP/3. Using cryptographic handshakes and X.509 digital certificates, it ensures data confidentiality, message integrity, and server identity verification—protecting headers, credentials, cookies, and payloads from eavesdropping or tampering in transit. Its scope covers the transport connection between the client and the TLS-terminating server, leaving application authorization and data stored at rest outside its direct protection.
Common Forms
Standard Server-Authenticated HTTPS: Relies on one-way TLS where only the server presents a certificate signed by a trusted Certificate Authority (CA), serving public websites and consumer APIs.
Mutual HTTPS (mTLS): Requires both client and server to present and verify X.509 certificates during the TLS handshake, commonly used in zero-trust microservice architectures and B2B APIs.
HSTS-Enforced HTTPS: Uses the
Strict-Transport-Securityresponse header to instruct browsers to reject plaintext HTTP and connect exclusively over HTTPS, mitigating protocol-downgrade attacks.HTTPS over QUIC (HTTP/3): Embeds the TLS 1.3 handshake directly inside QUIC over UDP instead of TCP, eliminating transport-layer head-of-line blocking and reducing connection latency.
Example
When a user submits login credentials to
https://bank.example.com/login, the browser connects on port 443, verifies the server's TLS 1.3 certificate chain, and negotiates ephemeral session keys before sending thePOSTrequest. Because the HTTP exchange travels inside the encrypted TLS stream, an eavesdropper on a public Wi-Fi network cannot inspect or tamper with the request headers, session cookie, or password payload.