Backend
Constructors
Properties
Bypass the cache when the specified request headers are matched - e.g. Pragma or Authorization headers. Up to 5 headers can be specified. The cache is bypassed for all cdnPolicy.cacheMode settings. Structure is documented below.
The CacheKeyPolicy for this CdnPolicy. Structure is documented below.
Specifies the default TTL for cached content served by this origin for responses that do not have an existing valid TTL (max-age or s-max-age). When the cache_mode is set to "USE_ORIGIN_HEADERS", you must omit this field.
Negative caching allows per-status code TTLs to be set, in order to apply fine-grained caching for common errors or redirects.
Sets a cache TTL for the specified HTTP status code. negativeCaching must be enabled to configure negativeCachingPolicy. Omitting the policy and leaving negativeCaching enabled will use Cloud CDN's default cache TTLs. Structure is documented below.
If true then Cloud CDN will combine multiple concurrent cache fill requests into a small number of requests to the origin.
Serve existing content from the cache (if available) when revalidating content with the origin, or when an error is encountered when refreshing the cache.
Maximum number of seconds the response to a signed URL request will be considered fresh. After this time period, the response will be revalidated before being served. When serving responses to signed URL requests, Cloud CDN will internally behave as though all responses from this backend had a "Cache-Control: public, max-age=TTL" header, regardless of any existing Cache-Control header. The actual headers served in responses will not be altered.