Clearing the Cache

When to Purge

You might need to purge cached content when:

• You've updated content at the origin and need to push changes immediately
• You've deployed a new version of your site and need to clear old assets
• You've found an error in cached content that needs to be corrected
• You've removed content that should no longer be accessible

Cache Size

Before purging, you can view the current cache size for your deployment. The Cache Size section shows real-time statistics about what's currently cached:

These statistics are aggregated across all domains in your deployment and update in real-time. After a purge, you'll see these numbers decrease as cached content is removed.

Purge Methods

https://cdn.yoursite.com/images/hero.jpg

/images/*
/assets/css/*

Purging via Console

1. Navigate to your CDN deployment
2. Click the Purge Cache button
3. Select a purge method (URL, Path, or Everything)
4. Enter the URL or path pattern (if applicable)
5. Click Purge

Purging via API

Integrate cache purging into your CI/CD pipeline using the Edge API.

# Purge specific URLs
curl -X POST https://api.edge.network/v1/cdn/deployments/:id/purge \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "urls": [
      "https://cdn.yoursite.com/images/hero.jpg",
      "https://cdn.yoursite.com/css/main.css"
    ]
  }'

# Purge by path prefix
curl -X POST https://api.edge.network/v1/cdn/deployments/:id/purge \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "paths": ["/images/*"]
  }'

# Purge everything
curl -X POST https://api.edge.network/v1/cdn/deployments/:id/purge \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "all": true
  }'

Purge Speed

Best Practices