Feature Overview

You can configure force redirect to forcibly redirect original requests that clients send to CDN points of presence (POPs) to HTTP requests or HTTPS requests. eSurfing Cloud CDN supports both HTTP force redirect and HTTPS force redirect. Force redirect is suitable for the following scenarios:

• If you have configured an HTTPS certificate for your accelerated domain name, you can configure force redirect to forcibly redirect HTTP requests sent from clients to CDN POPs to HTTPS requests using the 301 or 302 redirect method. HTTPS provides higher security.

• For a business application that has low security requirements, you can configure force redirect for the corresponding accelerated domain name to forcibly redirect HTTPS requests sent from clients to CDN POPs to HTTP requests using the 301 or 302 redirect method.

Procedure

Log in to the CDN console.
Go to Domain Management -> Domain List.
On the Domain List page, find the target domain name, and click Edit in the Actions column.
Click HTTPS .
Turn on the Force Redirect switch.
Select a redirect type. You can select Http->Https or Https->Http .
Select a redirect method. You can set the redirect method to 302 redirect or 301 redirect.
Click Save and Submit.

Additional Considerations

If HTTPS is disabled, you can configure only HTTPS-to-HTTP redirect. HTTP-to-HTTPS redirect is supported only if HTTPS is enabled and an HTTPS certificate is configured.

Content Delivery Network

Force redirection