Error Status Code Cache Expiration
Last updated
Was this helpful?
Last updated
Was this helpful?
The Error Status Code Cache Expiration feature in the Medianova Cloud Panel allows you to cache specified error codes (such as 404, 500, etc.) for a defined duration. By doing so, you can control how long error responses are stored in the CDN cache, reducing the number of requests sent to the origin server. If you don't want certain error codes to be cached, simply remove their definitions, and requests for those error codes will be sent directly to the origin server. However, if the content has already been cached, the cache duration will remain in effect until it expires.
Cache Error Status Codes: You can define a set of error codes (e.g., 404, 500, etc.) and specify a cache duration for each. This helps in reducing the load on your origin server by caching error responses for a certain period.
Removal of Caching Definition: If you remove a cached error status code definition, requests for that error will bypass the CDN cache and be sent directly to the origin server. However, cached content will not be affected immediately and will remain in the cache until the cache duration expires.
Click on the CDN Resources section in the left-hand menu of the Cloud panel.
Select the relevant resource.
Click on the Caching tab.
Navigate to the Error Status Code Cache Expiration section in the Medianova Cloud Panel.
Click the Add button to create a new definition.
Cache Time: Specify the cache duration for the error code (in seconds).
Status Code: Enter the HTTP status code(s) that you want to cache (e.g., 404, 500, etc.).
Add Multiple Definitions: You can add multiple error status codes and their respective cache durations by clicking the Add button repeatedly.
Once all necessary error codes and cache times are defined, click Submit to apply the changes.