Cloudflare Pages deploy issue traced to custom cache headers
A Cloudflare Pages user reported on September 28 that new deployments were not updating on production domains despite showing success status. The issue persisted for over a day, with both custom domains and .pages.dev URLs serving old content. Investigation revealed the problem originated from a custom s-maxage=604800 cache header applied to HTML files, overriding Cloudflare's default caching behavior. This header instructed CDN edge servers to retain the old HTML for up to a week, preventing new deployments from becoming visible.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)
Log in to join the discussion and vote.
Log in