Skip to content

HTTPS

HTTPS protects HTTP communication using TLS. Protected transport alone does not establish correct form processing or a user’s access rights.

Also known asHypertext Transfer Protocol Secure
Cloud & Operations

What does HTTPS mean?

HTTPS is the TLS-protected form of HTTP communication. MDN describes the encrypted connection between client and server. RFC9110 associates the HTTPS scheme with server authentication, confidentiality and integrity. The protection concerns communication with the respective connection endpoint.

Example: opening an enquiry form

In the fictional example, a person opens https://portal.studio.example/anfrage. The browser must verify the server against the name and transmit the HTTP request securely. The address is a placeholder; no real form is opened.

Even with protected transmission, the application must validate inputs, enforce permissions and process the result correctly. An HTTPS address does not prove that an enquiry was saved or that the page’s content is trustworthy.

At rollout, the team therefore checks certificates and the connection, as well as whether required pages and embedded resources actually load over suitable protected connections. HTTPS does not replace a complete functional test or a review of application permissions.

Sources

Articles on this topic

Cloud & Operations with ASES

Hosting, deployment, maintenance and support