Last update：2023-03-14 09:21:07
HTTPS has become the standard configuration for enterprises (Apple requires all iOS apps to use HTTPS connection, Google chrome browser labels HTTP websites as “not secure” ,etc.) as HTTPS effectively solve the problems of hijacking, tampering, and phishing that may arise in HTTP plain-text transmission.
CDNetworks can offer multiple HTTPS solutions for different customers. For HTTPS related features and solutions, we support:
TLS false start, HTTPS mutual authentication and SNI are standard and well known HTTPS features, so we do not go into details. This function manual focuses on introducing CDNetworks’ seamless deployment solution, double certificates deployment solution and keyless deployment solution.
When customers are willing to share their private key with us, we recommend them a regular deployment solution, where they can upload and deploy the certificates by themselves easily in SI portal.
CDNetworks provides a certificate management platform for customers to upload their public and private certificates to us. With Seamless HTTPS Acceleration solution, certificates can be deployed to CDN platform. After the certificates have been successfully deployed, the HTTPS requests from customers will be supported.
For the customers who are not willing to share their private key with CDNetworks due to security requirement, but willing to pay for another certificate, double certificates deployment solution is recommended.
CDNetworks can provide customers with another certificate (certificate A), which is used for setting up HTTPS connection with end users (Customer’s domain will be added into certificate A). When CDN sends request to origin server, HTTPS connection will be set up with customer’s own certificate (certificate B). In this way, we can support HTTPS communication between origin servers and end users without using customer’s private key.
If customers are:
we can provide keyless deployment solution to customers.
How Keyless deployment solution works