Overview

HTTPS ensures secure transmission through encryption and identity authentication. It is widely used in security-sensitive communications on the World Wide Web, such as online payment.

You can configure a domain name certificate for CDN PoPs. Then clients can use HTTPS to access CDN PoPs. If you want CDN to use HTTPS for origin pull, configure an HTTPS certificate for your origin server.
You can modify certificate settings of a domain name that is in the Enabled or Configuring state and is not locked or banned.

Function	Description
SCM Authorization	An SCM agency is required for SCM certificate configuration, so that you can directly obtain the certificate content when configuring SCM certifications in CDN.
Configuring an HTTPS Certificate	You can add a certificate on CDN PoPs to allow clients to access PoPs using HTTPS.
HTTPS Certificate Requirements	Describes the combination and upload sequence of certificates issued by different authorities
HTTPS Certificate Format Conversion	You can convert certificates in other formats to the PEM format that CDN supports.
TLS Versions	You can enable or disable Transport Layer Security (TLS) versions as required.
OCSP Stapling	You can allow CDN to cache the status of online certificates in advance and return the status to browsers. Browsers do not need to query the status from certificate authorities (CAs), accelerating the verification.
Force Redirect	You can configure force redirect to HTTP or HTTPS for requests from clients to CDN PoPs.
HSTS	You can configure HSTS to force clients (such as browsers) to use HTTPS to access your server, improving access security.
HTTP/2	Describes the background and advantages of HTTP/2.
QUIC	You can configure the QUIC protocol to improve transmission security, reduce transmission and connection latency, and prevent network congestion.