BackendServiceCdnPolicy class
Constructors
-
BackendServiceCdnPolicy({Input<BackendServiceCdnPolicyCacheKeyPolicy?>? cacheKeyPolicy, Input<String?>? cacheMode, Input<int?>? clientTtl, Input<int?>? defaultTtl, Input<int?>? maxTtl, Input<bool?>? negativeCaching, Input<List<BackendServiceCdnPolicyNegativeCachingPolicy>?>? negativeCachingPolicies, Input<bool?>? requestCoalescing, Input<int?>? serveWhileStale, Input<int?>? signedUrlCacheMaxAgeSec})
-
Creates a new BackendServiceCdnPolicy.
bypassCacheOnRequestHeaders Bypass the cache when the specified request headers are matched - e.g. Pragma or Authorization headers. Up to 5 headers can be specified.
cacheKeyPolicy The CacheKeyPolicy for this CdnPolicy.
cacheMode Specifies the cache setting for all responses from this backend.
clientTtl Specifies the maximum allowed TTL for cached content served by this origin.
defaultTtl Specifies the default TTL for cached content served by this origin for responses
maxTtl Specifies the maximum allowed TTL for cached content served by this origin.
negativeCaching Negative caching allows per-status code TTLs to be set, in order to apply fine-grained caching for common errors or redirects.
negativeCachingPolicies Sets a cache TTL for the specified HTTP status code. negativeCaching must be enabled to configure negativeCachingPolicy.
requestCoalescing If true then Cloud CDN will combine multiple concurrent cache fill requests into a small number of requests
serveWhileStale Serve existing content from the cache (if available) when revalidating content with the origin, or when an error is encountered when refreshing the cache.
signedUrlCacheMaxAgeSec Maximum number of seconds the response to a signed URL request
const
-
BackendServiceCdnPolicy.fromMap(Map<String, dynamic> map)
-
factory
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.
final
-
cacheKeyPolicy
→ Input<BackendServiceCdnPolicyCacheKeyPolicy?>?
-
The CacheKeyPolicy for this CdnPolicy.
Structure is documented below.
final
-
cacheMode
→ Input<String?>?
-
Specifies the cache setting for all responses from this backend.
The possible values are: USE_ORIGIN_HEADERS, FORCE_CACHE_ALL and CACHE_ALL_STATIC
Possible values are:
USE_ORIGIN_HEADERS, FORCE_CACHE_ALL, CACHE_ALL_STATIC.
final
-
clientTtl
→ Input<int?>?
-
Specifies the maximum allowed TTL for cached content served by this origin.
final
-
defaultTtl
→ Input<int?>?
-
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).
final
-
hashCode
→ int
-
The hash code for this object.
no setterinherited
-
maxTtl
→ Input<int?>?
-
Specifies the maximum allowed TTL for cached content served by this origin.
final
-
negativeCaching
→ Input<bool?>?
-
Negative caching allows per-status code TTLs to be set, in order to apply fine-grained caching for common errors or redirects.
final
-
negativeCachingPolicies
→ Input<List<BackendServiceCdnPolicyNegativeCachingPolicy>?>?
-
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.
final
-
requestCoalescing
→ Input<bool?>?
-
If true then Cloud CDN will combine multiple concurrent cache fill requests into a small number of requests
to the origin.
final
-
runtimeType
→ Type
-
A representation of the runtime type of the object.
no setterinherited
-
serveWhileStale
→ Input<int?>?
-
Serve existing content from the cache (if available) when revalidating content with the origin, or when an error is encountered when refreshing the cache.
final
-
signedUrlCacheMaxAgeSec
→ Input<int?>?
-
Maximum number of seconds the response to a signed URL request
will be considered fresh, defaults to 1hr (3600s). 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.
final
