/* * Copyright 2018-2023 Amazon.com, Inc. or its affiliates. All Rights Reserved. * * Licensed under the Apache License, Version 2.0 (the "License"). You may not use this file except in compliance with * the License. A copy of the License is located at * * http://aws.amazon.com/apache2.0 * * or in the "license" file accompanying this file. This file is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR * CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions * and limitations under the License. */ package com.amazonaws.services.lightsail.model; import java.io.Serializable; import javax.annotation.Generated; import com.amazonaws.protocol.StructuredPojo; import com.amazonaws.protocol.ProtocolMarshaller; /** *
* Describes the default cache behavior of an Amazon Lightsail content delivery network (CDN) distribution. *
* * @see AWS API * Documentation */ @Generated("com.amazonaws:aws-java-sdk-code-generator") public class CacheBehavior implements Serializable, Cloneable, StructuredPojo { /** ** The cache behavior of the distribution. *
** The following cache behaviors can be specified: *
*
* cache
- This option is best for static sites. When specified, your distribution caches and
* serves your entire website as static content. This behavior is ideal for websites with static content that
* doesn't change depending on who views it, or for websites that don't use cookies, headers, or query strings to
* personalize content.
*
* dont-cache
- This option is best for sites that serve a mix of static and dynamic content.
* When specified, your distribution caches and serve only the content that is specified in the distribution's
* CacheBehaviorPerPath
parameter. This behavior is ideal for websites or web applications that use
* cookies, headers, and query strings to personalize content for individual users.
*
* The cache behavior of the distribution. *
** The following cache behaviors can be specified: *
*
* cache
- This option is best for static sites. When specified, your distribution caches and
* serves your entire website as static content. This behavior is ideal for websites with static content that
* doesn't change depending on who views it, or for websites that don't use cookies, headers, or query strings to
* personalize content.
*
* dont-cache
- This option is best for sites that serve a mix of static and dynamic content.
* When specified, your distribution caches and serve only the content that is specified in the distribution's
* CacheBehaviorPerPath
parameter. This behavior is ideal for websites or web applications that use
* cookies, headers, and query strings to personalize content for individual users.
*
* The following cache behaviors can be specified: *
*
* cache
- This option is best for static sites. When specified, your distribution
* caches and serves your entire website as static content. This behavior is ideal for websites with static
* content that doesn't change depending on who views it, or for websites that don't use cookies, headers, or
* query strings to personalize content.
*
* dont-cache
- This option is best for sites that serve a mix of static and dynamic
* content. When specified, your distribution caches and serve only the content that is specified in the
* distribution's CacheBehaviorPerPath
parameter. This behavior is ideal for websites or web
* applications that use cookies, headers, and query strings to personalize content for individual users.
*
* The cache behavior of the distribution. *
** The following cache behaviors can be specified: *
*
* cache
- This option is best for static sites. When specified, your distribution caches and
* serves your entire website as static content. This behavior is ideal for websites with static content that
* doesn't change depending on who views it, or for websites that don't use cookies, headers, or query strings to
* personalize content.
*
* dont-cache
- This option is best for sites that serve a mix of static and dynamic content.
* When specified, your distribution caches and serve only the content that is specified in the distribution's
* CacheBehaviorPerPath
parameter. This behavior is ideal for websites or web applications that use
* cookies, headers, and query strings to personalize content for individual users.
*
* The following cache behaviors can be specified: *
*
* cache
- This option is best for static sites. When specified, your distribution
* caches and serves your entire website as static content. This behavior is ideal for websites with static
* content that doesn't change depending on who views it, or for websites that don't use cookies, headers,
* or query strings to personalize content.
*
* dont-cache
- This option is best for sites that serve a mix of static and dynamic
* content. When specified, your distribution caches and serve only the content that is specified in the
* distribution's CacheBehaviorPerPath
parameter. This behavior is ideal for websites or web
* applications that use cookies, headers, and query strings to personalize content for individual users.
*
* The cache behavior of the distribution. *
** The following cache behaviors can be specified: *
*
* cache
- This option is best for static sites. When specified, your distribution caches and
* serves your entire website as static content. This behavior is ideal for websites with static content that
* doesn't change depending on who views it, or for websites that don't use cookies, headers, or query strings to
* personalize content.
*
* dont-cache
- This option is best for sites that serve a mix of static and dynamic content.
* When specified, your distribution caches and serve only the content that is specified in the distribution's
* CacheBehaviorPerPath
parameter. This behavior is ideal for websites or web applications that use
* cookies, headers, and query strings to personalize content for individual users.
*
* The following cache behaviors can be specified: *
*
* cache
- This option is best for static sites. When specified, your distribution
* caches and serves your entire website as static content. This behavior is ideal for websites with static
* content that doesn't change depending on who views it, or for websites that don't use cookies, headers, or
* query strings to personalize content.
*
* dont-cache
- This option is best for sites that serve a mix of static and dynamic
* content. When specified, your distribution caches and serve only the content that is specified in the
* distribution's CacheBehaviorPerPath
parameter. This behavior is ideal for websites or web
* applications that use cookies, headers, and query strings to personalize content for individual users.
*
* The cache behavior of the distribution. *
** The following cache behaviors can be specified: *
*
* cache
- This option is best for static sites. When specified, your distribution caches and
* serves your entire website as static content. This behavior is ideal for websites with static content that
* doesn't change depending on who views it, or for websites that don't use cookies, headers, or query strings to
* personalize content.
*
* dont-cache
- This option is best for sites that serve a mix of static and dynamic content.
* When specified, your distribution caches and serve only the content that is specified in the distribution's
* CacheBehaviorPerPath
parameter. This behavior is ideal for websites or web applications that use
* cookies, headers, and query strings to personalize content for individual users.
*
* The following cache behaviors can be specified: *
*
* cache
- This option is best for static sites. When specified, your distribution
* caches and serves your entire website as static content. This behavior is ideal for websites with static
* content that doesn't change depending on who views it, or for websites that don't use cookies, headers, or
* query strings to personalize content.
*
* dont-cache
- This option is best for sites that serve a mix of static and dynamic
* content. When specified, your distribution caches and serve only the content that is specified in the
* distribution's CacheBehaviorPerPath
parameter. This behavior is ideal for websites or web
* applications that use cookies, headers, and query strings to personalize content for individual users.
*