Expected certificate behavior after moving to Pages?

Original message was deleted

Chaika•9/25/23, 10:13 PM

Is this the expected behavior?

Yes

Can a Pages site be configured to use the site-wide wildcard certificate?

No
The reason for it, is Pages uses CF for SaaS under the hood, which issues a certificate for your custom domain, and CF for SaaS certs always have higher priority then your Universal Cert (the *.example.com, example.com one):
https://developers.cloudflare.com/ssl/reference/certificate-and-hostname-priority/ (It's always as specific hostname/same zone)
The only way you'd get your own cert to show over Pages is if you manually uploaded your own on Business (Custom Modern/Legacy) Or Enterprise's Keyless SSL. Or if you used a worker to proxy your pages site and not a custom domain. That being said, it shouldn't really matter

Original message was deleted

Chaika•9/25/23, 11:24 PM

Sure no problem!

Pages uses CF for SaaS on the backend

If it helps to clarify, Pages uses CF for SaaS just for custom domains. It's essentially the same as the SSL/TLS -> Custom Hostnames in your own websites.
Pages uses Workers & KV for its backend

Expected certificate behavior after moving to Pages?

Similar Threads

Similar Threads

Similar Threads