Browser Active TTL
Browser Active TTL determines how long the file will be stored in the browser’s cache. Anycast CDN returns the headers, and the user’s browser utilizes its own cache for your content accordingly to the values you set here.
Additional cache settings
Min requests to cache — As shown on the picture above, you can change the number of file requests before the file gets cached. Until that request amount is reached, each request is redirected to the origin server to be served directly, and CDN is not caching the file. Default and recommended value is 1 as a preset, and the maximum is 10 requests.
When your Resource origin is Cloud Storage, Active TTL is mandatory and will be enabled automatically in case you switch to such a source.
Honor response TTL headers
If you add the following headers when distributing files:
X-Accel-Expires
Expires or
Cache-Control
the active Honor response TTL headers setting will override the TTL parameters set for the resource.
By default, headers are managed by the CDN, enable this feature if you want to inherit the origin’s headers.
To enable this feature, move the corresponding toggle into the active position, as depicted above.
When Honor Response TTL headers is enabled, the previously set Active TTL (Update Time To Live) and Browser Active TTL parameters for the resource will not be honored.