Error Status Code Cache Expiration
Configure how long specific HTTP error responses remain cached on CDN edge servers.
Last updated
Was this helpful?
Configure how long specific HTTP error responses remain cached on CDN edge servers.
Error Status Code Cache Expiration defines how long selected HTTP error responses (such as 404 or 500) stay valid in the CDN cache. This reduces repeated requests to the origin when the same error occurs frequently.
You can manage Error Status Code Cache Expiration in the Medianova Control Panel or via API.
Select a CDN resource in the CDN section, and navigate to the Caching tab.
Define a cache duration for specific HTTP error codes.
Click Add to Create a New Definition
Enter the Cache Time
Enter the duration (in seconds) for how long the selected error code should remain cached.
Enter the Status Code
Specify one or more HTTP status codes such as 404, 500, or 502.
Submit the Configuration
Click Submit to save the definition.
Modify the cache time or status code.
Click the Edit Icon Next to the Definition
Update the Cache Time or Status Code
Submit the Changes
Click Submit to apply updates.
Remove a cache rule so that future error responses bypass CDN cache.
Cached error responses remain valid until the configured cache time expires.
Deleting a definition does not immediately remove already cached error objects; existing cached content remains until expiration.
Setting a low cache duration minimizes the risk of serving error responses for extended periods.
If no definition exists for a status code, the CDN forwards all such responses to the origin without caching.
Does removing a definition purge already cached error responses? No. Existing cached content remains until it expires.
Can I cache multiple error codes with different durations? Yes. Each status code can have its own cache time.
What happens if I set the cache time to zero? A value of zero disables caching for that error status code.
Last updated
Was this helpful?
Was this helpful?