Edge Security Acceleration:UpdateCacheRule

The ID of the site. To get this ID, call the ListSites operation.

The configuration ID.

The rule name. Optional for global configurations.

Specifies whether to enable the rule. Optional for global configurations. Valid values:

• on: Enables the rule.

• off: Disables the rule.

A conditional expression that matches user requests. Optional for global configurations. Two scenarios are supported:

• To match all incoming requests, set the value to true.

• To match specific requests, set the value to a custom expression, for example, (http.host eq "video.example.com").

The cache bypass mode. Valid values:

• cache_all: Caches all requests.

• bypass_all: Bypasses the cache for all requests.

The browser cache mode. Valid values:

• no_cache: Does not cache content in the browser.

• follow_origin: Follows the caching policy of the origin server.

• override_origin: Overrides the caching policy of the origin server.

The browser cache TTL (Time to Live), in seconds.

The cache mode for the edge node. Valid values:

• follow_origin: Follows the origin server's caching policy. If the origin server has no policy, the default policy is used.

• no_cache: Does not cache content.

• override_origin: Overrides the caching policy of the origin server.

• follow_origin_bypass: Follows the caching policy of the origin server, if one exists. Otherwise, content is not cached.

• follow_origin_override: Follows the caching policy of the origin server, if one exists. Otherwise, a custom cache TTL is used.

The edge node cache TTL (Time to Live), in seconds.

The cache TTL for specific status codes, in seconds.

• You can set the cache TTL for a specific status code. For example, 404=10 caches responses with a 404 status code for 10 seconds.

• You can set the cache TTL for 4xx and 5xx status code ranges. For example, 4xx=10 caches all responses with a 4xx status code for 10 seconds.

• Separate multiple status code settings with commas.

Specifies whether to sort query string parameters when generating the cache key. Valid values:

• on: Enables sorting.

• off: Disables sorting.

Specifies how query strings are used to generate the cache key. Valid values:

• ignore_all: Ignores all query strings.

• exclude_query_string: Removes specified query strings.

• reserve_all: Retains all query strings. This is the default value.

• include_query_string: Retains only specified query strings.

The query string parameters to include in or exclude from the cache key. Separate multiple parameters with spaces.

The headers to include in the cache key. Both the header names (case-insensitive) and their values are used. Separate multiple headers with spaces. Header names can contain the following characters:

• Symbols: ! # $ % & ' * + - . ^ _ | ~

• Digits: 0-9

• Lowercase letters: a-z

The cookies to include in the cache key. Both the cookie names (case-insensitive) and their values are used. Separate multiple cookies with spaces. Cookie names can contain the following characters:

• Symbols: ! # $ % & ' * + - . ^ _ | ~

• Digits: 0-9

• Lowercase letters: a-z

Specifies whether requests bypass the cache reserve node during an origin-pull. Valid values:

• bypass_cache_reserve: The request bypasses the cache reserve.

• eligible_for_cache_reserve: The request is eligible for cache reserve.

The headers to check for. If a specified header is present in the request, its name (case-insensitive) is added to the cache key. Separate multiple headers with spaces. Header names can contain the following characters:

• Symbols: ! # $ % & ' * + - . ^ _ | ~

• Digits: 0-9

• Lowercase letters: a-z

The cookies to check for. If a specified cookie is present in the request, its name (case-insensitive) is added to the cache key. Separate multiple cookies with spaces. Cookie names can contain the following characters:

• Symbols: ! # $ % & ' * + - . ^ _ | ~

• Digits: 0-9

• Lowercase letters: a-z

Specifies whether to include the client device type in the cache key. Valid values:

• on: Enables this feature.

• off: Disables this feature.

Specifies whether to include the client geographic location in the cache key. Valid values:

• on: Enables this feature.

• off: Disables this feature.

Specifies whether to include the client language in the cache key. Valid values:

• on: Enables this feature.

• off: Disables this feature.

Specifies whether to serve stale content. If enabled, an edge node serves expired cached content when the origin server is unavailable. Valid values:

• on: Enables this feature.

• off: Disables this feature.

• Enables caching on the specified ports.

• Valid values: 8880, 2052, 2082, 2086, 2095, 2053, 2083, 2087, 2096

• Separate multiple ports with commas.

Defends against Web Cache Deception attacks by caching only validated content. Valid values:

• on: Enables the feature.

• off: Disables the feature.

The execution priority of the rule. A smaller value indicates a higher priority.

Specifies whether to cache responses to POST requests.

The maximum request body size for POST caching, in KB. Valid values: 1 to 8. Default value: 8.

Specifies how the request body is used to generate the cache key for POST requests. Valid values:

• md5: Calculates the MD5 hash of the request body and includes the hash in the cache key.

• ignore: Ignores the request body when generating the cache key.