Cache override

Modifies backend cache headers to enforce behaviors such as Always cache, Bypass cache, Expiration, or Custom settings.

This action changes the cache-related headers that originate from the backend, letting you control how a matching resource is cached by Webscale and downstream caches.

Configuration

  • Always cache: Allows the resource to be cached by Webscale ADCs and any downstream caches, including web browsers. This also allows optimizations to be applied to the resource.
  • Bypass cache: Sets the Cache-Control header to no-cache, informing all downstream caches, including the browser, not to cache the resource. This also prevents any optimization of the resource.
  • Expiration: Adds a Cache-Control header that expires at a selected time. For a more specific expiration time, use the Custom setting.
  • Custom: Sets the contents of the Cache-Control header value directly, used as-is when valid, in place of the value returned from the application server. Note that max-age is measured in seconds.

Behavior

When the conditions of the web control are met, the proxy modifies the cache-related headers of the response according to the selected setting before the response is cached or returned to the client.

Have questions not answered here? Contact Support to get more help.

Last modified on November 18, 2026