The Secure Sockets Layer protocol for Static services on our platform allows you to access BlazingCDN services via HTTPS. If SSL is not enabled for BlazingCDN, HTTPS access will throw an SSL error because the CDN will not match the SSL certificate used for the HTTPS connection. For creating BlazingCDN with enabling SSL protocol, log in to your dashboard, then go to Anycast CDN and Pull Zone List. Then click Create new pull zone.
The next step is pushing a line of the desired CDN. You need to use a valid domain name. Enter also your Origin domain name and select the appropriate encryption protocol (HTTP / HTTPS).
Then, in the Anycast CDN and Pull ZOne list sections, go to the Preferences section. Scroll down. You have the Enable HTTPS encrypted toggle here, and then you have the Shared SSL box to choose from. The shared SSL certificate is installed globally on the server and is designed to protect all clients on the computer. Then click Apply, and you’re done.
See also:
Using HTTP/2 w BlazingCDN
Setting up BlazingCDN for SEO
Setting a Cache in BlazingCDN
Restricting access to BlazingCDN origin server
Origin Protocol in BlazingCDN
Origin Port in BlazingCDN
Manage content in the BlazingCDN cache
How to accelerate website with BlazingCDN
Cookies in BlazingCDN
BlizngCDN Origin protection
BlazingCDN URL Signing
BlazingCDN Static service
BlazingCDN Service Domains
BlazingCDN recommended Gzip compression
BlazingCDN Password
BlazingCDN Origin Domains Setup
BlazingCDN Hotlinking Policy
BlazingCDN Flash files – cross-domain cases
BlazingCDN and IP Access Policy
BlazingCDN and Cloudflare
BlazingCDN and Amazon S3
BlazingCDN Access Policy
BlaizngCDN server limits