proxy_ssl_ca is the public CA certificate that checks the origin certificate, while proxy_ssl_data is an uploaded certificate and private key that the edge presents when the origin requests a client certificate.
An API token is required, along with a CDN resource configured for HTTPS origin pull, a CA certificate to store as
proxy_ssl_ca, and an uploaded SSL certificate to send as proxy_ssl_data.Add a trusted CA certificate
Upload the CA certificate that issued the origin certificate. If the origin certificate is self-signed, upload that certificate itself. A trusted CA request stores that public certificate and returns the id forproxy_ssl_ca.
- Python SDK
- Go SDK
- curl
Get the SSL certificate ID
Use the id of the uploaded client certificate and private key asproxy_ssl_data. This object is separate from the trusted CA.
A certificate list returns the id of the certificate with that name.
- Python SDK
- Go SDK
- curl
Enable validation on the resource
The first resource update requires both certificate ids even when the origin does not request a client certificate. Omitting either id returns HTTP 400 with the messageCan not enable proxy_ssl feature while both proxy CA certificate and proxy ssl data not specified.
- Python SDK
- Go SDK
- curl
proxy_ssl_ca and proxy_ssl_data refer to different certificate collections. Sending an SSL certificate id as proxy_ssl_ca, or a trusted CA id as proxy_ssl_data, returns HTTP 400 with the message Invalid pk "1003" - object does not exist.Disable validation on the resource
The same update turns validation off whenproxy_ssl_enabled is false and keeps both certificate ids. A later update can set proxy_ssl_enabled to true alone, because those ids are already stored.
- Python SDK
- Go SDK
- curl