Package com.pulumi.gcp.compute.outputs

Class BackendServiceCdnPolicy

  • public final class BackendServiceCdnPolicy
extends java.lang.Object

    • Method Detail

      • bypassCacheOnRequestHeaders

        public java.util.List<BackendServiceCdnPolicyBypassCacheOnRequestHeader> bypassCacheOnRequestHeaders()
        Returns:
        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.

      • cacheMode

        public java.util.Optional<java.lang.String> cacheMode()
        Returns:
        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`.

      • clientTtl

        public java.util.Optional<java.lang.Integer> clientTtl()
        Returns:
        Specifies the maximum allowed TTL for cached content served by this origin.

      • defaultTtl

        public java.util.Optional<java.lang.Integer> defaultTtl()
        Returns:
        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).

      • maxTtl

        public java.util.Optional<java.lang.Integer> maxTtl()
        Returns:
        Specifies the maximum allowed TTL for cached content served by this origin.

      • negativeCaching

        public java.util.Optional<java.lang.Boolean> negativeCaching()
        Returns:
        Negative caching allows per-status code TTLs to be set, in order to apply fine-grained caching for common errors or redirects.

      • negativeCachingPolicies

        public java.util.List<BackendServiceCdnPolicyNegativeCachingPolicy> negativeCachingPolicies()
        Returns:
        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.

      • serveWhileStale

        public java.util.Optional<java.lang.Integer> serveWhileStale()
        Returns:
        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

        public java.util.Optional<java.lang.Integer> signedUrlCacheMaxAgeSec()
        Returns:
        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.