Edge Cache Expiration

Learn how to configure how long content remains cached on CDN edge servers.

Edge Cache Expiration controls whether CDN edge servers cache an object and how long the cached content remains valid before it must be refreshed from the origin.

It defines the caching behavior applied at the edge, including modes that disable caching entirely or defer expiration settings to the origin.

You can manage Edge Cache Expiration in the Medianova Control Panel or via API.

Configure Edge Cache Expiration

Use this workflow to define how the CDN determines cache duration and applies expiration rules on edge servers.

1

Access the Edge Cache Expiration

This feature is located under the Caching tab in any CDN Resource. This section includes the Cache Type selector and expiration time fields.

2

Select the Cache Type

Choose how the CDN evaluates cache duration:

Edge — The CDN applies the expiration time configured in the Panel. A value of 0 disables caching. Origin — The CDN honors cache headers sent by the origin. If no cache duration is provided, the Panel-defined value applies. A value of 0 disables caching. Dynamic — The CDN does not cache the content. All requests always forward to the origin regardless of origin headers or Panel settings.

The Edge Cache Expiration section allows configuration of the Cache Type and duration settings.
3

Enter the expiration time

Specify how long content should remain cached on edge servers. For Origin mode, this value is applied only when the origin provides no cache duration.

4

Save the configuration

Click Submit to apply the updated caching rules across the CDN network.

  • A value of 0 disables caching for both Edge and Origin modes.

  • Dynamic mode always bypasses caching on edge servers.

  • These settings do not impact browser caching; use Browser Cache Rule for client-side caching behavior.

Best Practices

  • Apply long TTL values for static assets such as images, fonts, CSS, and JavaScript.

  • Use shorter TTL values for frequently updated or dynamic endpoints.

  • Monitor edge cache hit ratios to optimize performance and origin load.

Last updated

Was this helpful?