Got a Docker Compose file? Your project goes live in seconds — one command on cdn.com.tr. See how Built your app with AI? From folder to live URL with one command — no git, no registry: cdnctl deploy. See how Code on GitHub? Every push auto-deploys to cdn.com.tr — connect your repo and ship. See how

CDN.com.tr Help

Old content still shows after a deploy

Separate CDN cache from browser cache, purge the right path, and verify with clean requests.

Troubleshooting and status glossary

Old content still shows after a deploy

Separate CDN cache from browser cache, purge the right path, and verify with clean requests.

Use cases

A customer deployed new CSS, JS, or HTML to the origin, but visitors (or the customer) still see the previous version.

Workflow

  1. First verify the origin really serves the new content (request the origin directly or check the deploy).
  2. Test the public URL with `curl -I` or a private browser window — a normal reload can show your own browser cache, not the CDN.
  3. Check the `X-Proxy-Cache-MT` header: HIT with old content means the CDN cache needs a purge.
  4. Open Purge Management and purge the changed paths (or use a saved path set for releases).
  5. Request the URL again: expect MISS, then HIT with the new content.

Checks

  • Browser cache and CDN cache are different layers; a hard refresh only clears the first.
  • Purging `/` does not purge every page — purge the specific changed paths or use purge-all deliberately.
  • If your asset URLs include a version query string (`app.css?v=123`), bumping the version is often better than purging.

Frequently asked questions

I purged but still see the old page.

Check whether the response is now MISS (purge worked, browser cache is the leftover — use a private window) or still HIT (the purge path did not match — purge the exact path including locale prefixes or query strings).

Do I need to purge after every deploy?

Only for URLs whose content changed but whose path stayed the same. Versioned asset URLs avoid this entirely; HTML pages usually need a purge or a short TTL.

Why do mobile users still see old content after a purge?

Mobile is not cached separately — a purge clears the same entry for both devices. Content that stays old on a phone is almost always the visitor's own browser cache; confirm with a hard refresh or a private tab.

Related pages

Status message glossary

Understand Waiting DNS, SSL pending, healthcheck failed, object storage gated, and similar statuses.