Stale Cache
The Stale Cache feature in the Medianova Cloud Panel allows you to serve stale (previously cached) content when certain HTTP error codes or an "Updating" status is encountered. This ensures uninterrupted availability of content during temporary origin server issues or while content is being updated.
Key Features
Maintain Availability: Serve cached content even when the origin server experiences temporary issues or returns specific error codes.
Customizable Error Triggers: Select which HTTP error codes or the "Updating" status should activate the use of stale cached content.
Improved User Experience: Reduces downtime and ensures users continue to access content even during backend disruptions.
Supported Triggers
You can configure the system to serve stale cached content when any of the following statuses are detected:
Updating: Triggered when content is in the process of being updated.
HTTP_500: Internal Server Error.
HTTP_502: Bad Gateway.
HTTP_503: Service Unavailable.
HTTP_504: Gateway Timeout.
HTTP_403: Forbidden.
HTTP_404: Not Found.
HTTP_429: Too Many Requests.
How to Configure Stale Cache
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 Stale Cache section in the Medianova Cloud Panel.
Activate the Stale Cache option to configure the settings.
Select Error Triggers:
Choose the HTTP error codes (e.g., 500, 502, 503, etc.) or Updating status that will trigger the use of stale cached content.
Multiple triggers can be selected simultaneously.
Click Submit to apply your configurations.
Last updated
Was this helpful?
