> For the complete documentation index, see [llms.txt](https://docs.serverlessapigateway.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.serverlessapigateway.com/glossary/h/https-hypertext-transfer-protocol-secure.md). # HTTPS (Hypertext Transfer Protocol Secure) An extension of HTTP. It is used for secure communication over a computer network, and is widely used on the Internet. HTTPS is the secure version of HTTP, using TLS (Transport Layer Security) encryption to protect data in transit between the client and server. HTTPS ensures three key security properties: confidentiality (data cannot be read by intermediaries), integrity (data cannot be modified in transit), and authentication (the server's identity is verified through its TLS certificate). HTTPS requires a valid TLS certificate issued by a Certificate Authority (CA). Certificates can be obtained from providers like Let's Encrypt (free) or commercial CAs. The TLS handshake establishes an encrypted connection before any HTTP data is exchanged. Modern best practices mandate HTTPS for all web traffic, not just pages handling sensitive data. For APIs, HTTPS is essential. All API traffic should be encrypted to protect API keys, authentication tokens, and payload data. API gateways typically handle TLS termination, decrypting incoming HTTPS requests and forwarding them to backend services over internal networks. This centralizes certificate management and offloads the computational cost of encryption from backend services. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.serverlessapigateway.com/glossary/h/https-hypertext-transfer-protocol-secure.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.