CDN.com.tr Help

Purge cached content

Purge a path, saved path, or the whole account and separate CDN cache from browser cache.

Back to Help Center Back to section

Cache, security, WAF, and purge

Purge cached content

Purge a path, saved path, or the whole account and separate CDN cache from browser cache.

Panel path

  1. Management Panel
  2. CDN Accounts
  3. Purge Management
  4. Path purge / Purge all
  5. Operations

Prerequisites

  • Purge path must belong to the selected account.
  • Purge all should be used intentionally and sparingly.
  • Browser cache and CDN cache must be separated during verification.

Step-by-step guide

1

Choose purge target

Single file, folder/prefix, and whole-cache purge have different risk levels.

  • Open Purge Management.
  • Enter path or choose saved path.
  • Confirm scope when using purge all.

Expected result: The purge request is created in the selected account scope.

cdnctl equivalent 
cdnctl purge create --account <account_uuid> --path /assets/app.css
2

Verify purge result

After purge completes, verify with a clean browser session or response headers.

  • Check purge status from Operations.
  • Reopen URL with cache bypass or a clean session.

Expected result: CDN stops returning the stale object.

cdnctl equivalent 
cdnctl operations list --account <account_uuid>
curl -I https://<hostname>/<path>

Verification

  • Path is purged for the right account/domain.
  • Purge all requires customer confirmation.
  • Result is verified through public URL or headers.

Use cases

A deployment is live on origin but CDN still returns the old asset.

Quick workflow

  1. Open Purge Management.
  2. Enter path or choose saved path.
  3. Start purge.
  4. Check purge-all status or operation state.

Checks

  • Path belongs to selected account.
  • Purge all is intentionally confirmed.
  • Browser cache is ruled out before retry.

Related pages

Read WAF logs

Use WAF logs to explain blocked or challenged traffic without exposing internal log systems.