Google Cloud Compute V1 API - Module Google::Cloud::Compute::V1::BackendServiceCdnPolicy::CacheMode (v2.15.0)

Reference documentation and code samples for the Google Cloud Compute V1 API module Google::Cloud::Compute::V1::BackendServiceCdnPolicy::CacheMode.

Specifies the cache setting for all responses from this backend. The possible values are: USE_ORIGIN_HEADERS Requires the origin to set valid caching headers to cache content. Responses without these headers will not be cached at Google's edge, and will require a full trip to the origin on every request, potentially impacting performance and increasing load on the origin server. FORCE_CACHE_ALL Cache all content, ignoring any "private", "no-store" or "no-cache" directives in Cache-Control response headers. Warning: this may result in Cloud CDN caching private, per-user (user identifiable) content. CACHE_ALL_STATIC Automatically cache static content, including common image formats, media (video and audio), and web assets (JavaScript and CSS). Requests and responses that are marked as uncacheable, as well as dynamic content (including HTML), will not be cached. If no value is provided for cdnPolicy.cacheMode, it defaults to CACHE_ALL_STATIC.

Constants

UNDEFINED_CACHE_MODE

value: 0
A value indicating that the enum field is not set.

CACHE_ALL_STATIC

value: 355_027_945
Automatically cache static content, including common image formats, media (video and audio), and web assets (JavaScript and CSS). Requests and responses that are marked as uncacheable, as well as dynamic content (including HTML), will not be cached.

FORCE_CACHE_ALL

value: 486_026_928
Cache all content, ignoring any "private", "no-store" or "no-cache" directives in Cache-Control response headers. Warning: this may result in Cloud CDN caching private, per-user (user identifiable) content.

INVALID_CACHE_MODE

value: 381_295_560

USE_ORIGIN_HEADERS

value: 55_380_261
Requires the origin to set valid caching headers to cache content. Responses without these headers will not be cached at Google's edge, and will require a full trip to the origin on every request, potentially impacting performance and increasing load on the origin server.