All Products
Search
Document Center

Edge Security Acceleration:Force HTTPS

Last Updated:Feb 27, 2026

You can configure the force redirect to HTTPS feature to redirect client requests that are sent to Edge Security Acceleration (ESA) POPs to the more secure HTTPS protocol.

Use case

The Always Use HTTPS feature is typically used to improve website security and protect user data. When an ESA POP receives an HTTP request from a client, it redirects the request to the more secure HTTPS protocol using an HTTP 301 status code.

image

Notes

  • Before you configure redirection to HTTPS, make sure that you have configured an SSL/TLS certificate for your site as described in Configure an edge certificate. For more information, see Configure an edge certificate.

  • After enabling Always Use HTTPS, if your application still references non-encrypted HTTP resources, visitors' browsers may display a "Mixed Content" warning.

Enable Always Use HTTPS

  1. In the ESA console, go to Websites. In the Website column, click your target site.

  2. In the navigation pane on the left, choose Edge Certificates.

  3. Enable Always Use HTTPS.

    image

Site-level and rule-based features mapping

A site-wide configuration applies to all requests for that site. To apply Always Use HTTPS only to specific requests, use the rule-based feature instead. You can define rules with conditions that detect specific parameters in client requests. This gives you precise control over which requests the rule affects. The rule-based equivalent of the site-wide Always Use HTTPS feature is HTTPS rules.