If you do not want the Atomile CDN platform to cache file resources that contain certain response headers, you can configure this behavior with a few simple settings. With this custom configuration, when a user request receives a response containing the specified header, the CDN node bypasses the cache, fetches the file directly from your origin server, and returns it to the user.

For subsequent requests for the same file, the CDN node again fetches the file from the origin server and returns it without caching it. Currently, you can configure CDN nodes not to cache files whose responses contain the Location or Set-Cookie header.

How to Configure No Caching Based on Response Headers

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 Cache Bypass under Cache Optimization. On the right side of the page, select Location or Set-Cookie under the Response Header field as needed.

Parameter	Description
Location	By default, CDN servers do not cache content returned from your origin with status code 302, unless an expiration header such as Expires or Cache-Control: max-age is also present. For status code 301, CDN servers cache the content unless the origin returns a no-cache header or a custom non-caching rule has been configured as described in Set Cache Rules. If you select Location for non-caching, CDN servers do not cache content returned from your origin with a Location header, regardless of whether the status code is 301 or 302.
Set-Cookie	If Set-Cookie is selected, any content returned from your origin server with a Set-Cookie header is not cached by 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

When this feature is enabled, if your origin server responds with the specified headers, the corresponding content is not cached on CDN servers. As a result, every such user request triggers a new fetch from the origin server, which may increase origin load.