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

Purge cached content

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

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 
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

The Security page: WAF, IP and country blocking, hotlink, rate limit

All account-level security controls live on one Security page: the site-wide WAF toggle, JS Challenge bot protection, IP and country blocking, hotlink protection, request rate limiting, and link expiration. Every save deploys to the edge automatically — no separate publish step.

Block traffic by ASN and by country

Two account-wide blacklists on the same panel: block whole countries by country code, or block whole networks by autonomous system number. A blocked visitor gets the branded 403 page with a Reference ID.

Turn on HSTS for your hostnames

The Hsts security preset makes the edge send Strict-Transport-Security: max-age=31536000 on HTTPS responses, so a browser that has seen your site once refuses to open it over plain HTTP for a year.

Read WAF logs

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

Signed URLs: links that expire

Protect a file so it can only be fetched with a signature you generate, valid until a moment you choose. Unsigned requests get 403, expired ones get 410.

Image optimization: AVIF and WebP at the edge

Switch on image optimization for the account or for one delivery rule and choose WebP or WebP + AVIF: the edge converts JPEG and PNG images and sends each browser a format it accepts, while your pages keep the same image URLs.