Documentation Cache Settings Cache the Error Status Code

Cache the Error Status Code

Last update:2026-07-13 18:22:56

Based on the HTTP error status codes returned by your origin server, you can configure simple settings on the Atomile CDN platform to define how long the corresponding error pages are cached on CDN servers. This feature can help significantly reduce origin load by minimizing repeated origin fetches when CDN servers do not already have cached responses for malicious or repeated invalid requests.

By default, CDN servers do not cache error pages returned by your website for most error status codes.

How to Configure Error Status Code Caching TTL

  1. Log in to the Atomile Console and select the appropriate product.
  2. Go to Configuration, locate the domain you want to configure, and click Edit Configuration at the top or the Edit button to the right of the domain.
  3. On the configuration page, find Status Code Cache TTL under Cache Optimization, and click Add.
  4. On the rule editing page, configure the following options as needed.

The configurable items are as follows:

Parameter Description
Status Code Enter the origin response status codes for which CDN servers should cache the corresponding error page. The platform supports the following status codes: 204; 305; 400; 403; 404; 405; 414; 416; 423; 429; 500; 501; 502; 503; 504.
Note: By default, the error page for status code 404 is cached for 1 minute.
Cache TTL Configure how long the error page for the specified status codes is cached on CDN servers. The currently supported time units are seconds, minutes, and hours.
If the cache time is set to 0, the page is not cached on CDN servers.

After completing the configuration, click OK, and then click Next to submit your settings. To minimize potential disruption to your production environment, we strongly recommend performing a Pre-deploy test in a staging environment. This important step ensures that your configuration is correct before it goes live.

After you confirm that the settings are correct, click Deploy Now to apply them in the live environment. The configuration typically takes effect within 3 to 5 minutes. For more information about pre-deployment testing and validation, refer to Deploy the Configurations to Staging Environment for Validation.

Notes

If you configure a long cache duration for error pages on CDN servers, the CDN servers return the cached error page directly to users during that cache period. Therefore, use caution when setting the cache duration if you may need to return a different file or updated response to clients within a shorter time.