1

We have a cloudflare page with custom domain, eg.:

  1. Page: xxxxxx-frontend-about.pages.dev
  2. Custom domain about.xxxxxxxx.co

We deployed a new version and we could se that the (1) was updated, but (2) was not and we could see age: 6456.

I guess it is not intentional and the cache for the page should be purged after deployment?

Vojtěch
  • 11,312
  • 31
  • 103
  • 173

1 Answers1

0

This is because your custom domain, which has a CNAME record pointing to the cloudflare page is proxied. This is completely redundant, as cloudflare already handles DDOS protection and caching at the page level, without the need to proxy the custom domain.

To fix this, you have to go into your Cloudflare's DNS section, click edit on the record pointing to your cloudflare page amd switch the Proxy status option from 'Proxied' to 'DNS only'.

This means the website will now be shown with it's intended cache which is always automatically purged after each deployment.

woodendoors7
  • 92
  • 1
  • 11