Purge

Instantly invalidate outdated cache entries across all Medianova CDN cache layers to ensure the latest content is delivered globally without waiting for TTL expiration.

Purge invalidates cached content across the Medianova CDN before its cache lifetime (TTL) expires. It ensures that updated content from your origin is immediately reflected and consistently served from all cache layers worldwide.

When a purge is executed, the Medianova purge system distributes invalidation commands across the CDN’s cache hierarchy. Cached objects are marked as expired and fetched again from your origin upon the next user request.

You can trigger a purge from the Medianova Control Panel or via API .

When to Purge Cached Content

Use purge whenever:

• Updated HTML, CSS, JS, images, or video files must be reflected immediately.

• Outdated or sensitive content needs to be removed from CDN caches.

• New deployments or configuration changes require instant cache refresh.

• Consistency across all cache layers is required after a content update.

Combine purge operations with shorter TTL values for dynamic or frequently changing content.

Types of Purge

Medianova supports multiple purge methods to give you flexibility and control:

Type	Description	Example
Single File Purge	Removes one specific file from all CDN caches.	/images/banner.jpg
Wildcard Purge	Removes multiple files using pattern matching.	/images/*
Full CDN Resource Purge	Clears all cached files for a specific CDN Resource.	/*

Wildcard purge operations are recursive and affect all subdirectories. To use wildcard patterns, the Wildcard Purge Suffix option must be enabled under CDN Settings.

How Purge Works

1. A purge request is initiated via the Medianova Control Panel or API.

2. Medianova’s purge system distributes invalidation commands to all cache layers.

3. Cached objects matching the path are marked as invalid and no longer served.

4. On the next user request, the CDN retrieves the fresh content from the origin and re-caches it.

Cache propagation completes rapidly, depending on node density, region count, and network conditions.

Purge Propagation & Behavior

Purge requests propagate through all layers of Medianova’s caching infrastructure extremely quickly – typically completing across our global network in under 5 seconds – ensuring that outdated content is swiftly replaced with fresh content worldwide.

Behavior	Description
Instant Global Invalidation	Cache invalidations propagate rapidly across all CDN cache layers.
Parallel Distribution	Purge commands are broadcast concurrently to all cache nodes for faster execution.
Independent Caches	Each CDN node manages its local cache separately; purge ensures global synchronization.
Auto Revalidation	After purge, next requests trigger fresh pulls from the origin.

A full purge (/*) removes all cached files for that resource and should be used only when necessary.

Best Practices

• Purge only what’s needed. Avoid full purges to reduce cache refill load.

• Use specific paths instead of broad wildcard patterns whenever possible.

• Automate with API purge to clear cache after deployments or content updates.

• Monitor purge logs to verify completion (see Manage Purge).

• Coordinate with TTL strategy. If content changes often, use shorter cache durations.