Purge

Instantly remove outdated or updated content from Medianova CDN edge caches to ensure your users always receive the latest version of your files.

Purge is the process of removing cached content from Medianova CDN edge servers before its cache lifetime (TTL) expires. It’s typically used when you’ve updated files on your origin and need those changes to be reflected immediately without waiting for automatic cache expiration.

When you perform a purge, Medianova sends invalidation requests to all edge nodes storing the specified files, ensuring consistent and up-to-date delivery across the global CDN network.

Purge can be triggered through the Medianova Control Panel or via API .

Why Use Purge?

Use the purge feature whenever:

• You’ve updated assets (HTML, CSS, JS, images, videos) and need them live immediately.

• You want to remove outdated or sensitive content cached across the CDN.

• You deploy new application versions or run frequent content updates.

• You want to maintain consistent user experience across all edge locations.

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 Control Panel or API.

2. Medianova’s purge system distributes the request to all edge servers containing the specified objects.

3. Cached copies are deleted or marked invalid, depending on configuration.

4. The next user request for that file will fetch the updated version directly from your origin.

Propagation Time: Purge requests are processed asynchronously across all edge locations. Actual propagation time depends on system load and global node count. (confirm average purge completion time with the CDN engineering team.)

Purge Propagation & Behavior

Behavior	Description
Asynchronous Invalidation	Purge requests may complete at slightly different times across regions.
Recursive Wildcard Handling	/example/images/* clears all subdirectories within /example/images/.
Independent Edge 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.