The G-Core Labs CDN uses advanced technology to protect and secure content delivery.
To enhance security, we’ve built an origin server authentication mechanism into the content retrieval process.
When configuring the protocol for interaction with the origin, you specify the protocol by which the CDN servers will contact the origin for content. You can decide whether the connection should be encrypted (HTTPS) or not (HTTP).
If HTTPS is selected, cache servers will access and receive content from the origin over HTTPS. This process is encrypted but it doesn’t protect against man-in-the-middle attacks because, by default, the cache server doesn’t check whether the responding server belongs to the client when requesting content.
To ensure the security of the transmitted data, use the “Validate origin using SSL” option.
This option also allows clients to check the validity of requests from our cache servers without using a list of IP addresses and constantly updating it.
You specify the PEM-encoded public part of the X.509 digital certificate in our system. The other part of the certificate is stored on your origin server. Each certificate in the system is assigned its own identifier, and this information is stored on each CDN server. You can request information about a certificate (or about all certificates available in the system) and change its name at any time.
For now, this feature can only be enabled via API.