/**
* Copyright Amazon.com, Inc. or its affiliates. All Rights Reserved.
* SPDX-License-Identifier: Apache-2.0.
*/
#pragma once
#include Inspect all headers in the web request. You can specify the parts of the
* headers to inspect and you can narrow the set of headers to inspect by including
* or excluding specific keys. This is used to indicate the web request
* component to inspect, in the FieldToMatch specification. If you
* want to inspect just the value of a single header, use the
* Example JSON: SingleHeader
FieldToMatch
setting instead."Headers": { "MatchPattern": { "All": {} }, "MatchScope":
* "KEY", "OversizeHandling": "MATCH" }
See Also:
AWS API
* Reference
The filter to use to identify the subset of headers to inspect in a web * request.
You must specify exactly one setting: either All
,
* IncludedHeaders
, or ExcludedHeaders
.
Example
* JSON: "MatchPattern": { "ExcludedHeaders": [ "KeyToExclude1",
* "KeyToExclude2" ] }
The filter to use to identify the subset of headers to inspect in a web * request.
You must specify exactly one setting: either All
,
* IncludedHeaders
, or ExcludedHeaders
.
Example
* JSON: "MatchPattern": { "ExcludedHeaders": [ "KeyToExclude1",
* "KeyToExclude2" ] }
The filter to use to identify the subset of headers to inspect in a web * request.
You must specify exactly one setting: either All
,
* IncludedHeaders
, or ExcludedHeaders
.
Example
* JSON: "MatchPattern": { "ExcludedHeaders": [ "KeyToExclude1",
* "KeyToExclude2" ] }
The filter to use to identify the subset of headers to inspect in a web * request.
You must specify exactly one setting: either All
,
* IncludedHeaders
, or ExcludedHeaders
.
Example
* JSON: "MatchPattern": { "ExcludedHeaders": [ "KeyToExclude1",
* "KeyToExclude2" ] }
The filter to use to identify the subset of headers to inspect in a web * request.
You must specify exactly one setting: either All
,
* IncludedHeaders
, or ExcludedHeaders
.
Example
* JSON: "MatchPattern": { "ExcludedHeaders": [ "KeyToExclude1",
* "KeyToExclude2" ] }
The filter to use to identify the subset of headers to inspect in a web * request.
You must specify exactly one setting: either All
,
* IncludedHeaders
, or ExcludedHeaders
.
Example
* JSON: "MatchPattern": { "ExcludedHeaders": [ "KeyToExclude1",
* "KeyToExclude2" ] }
The parts of the headers to match with the rule inspection criteria. If you
* specify All
, WAF inspects both keys and values.
The parts of the headers to match with the rule inspection criteria. If you
* specify All
, WAF inspects both keys and values.
The parts of the headers to match with the rule inspection criteria. If you
* specify All
, WAF inspects both keys and values.
The parts of the headers to match with the rule inspection criteria. If you
* specify All
, WAF inspects both keys and values.
The parts of the headers to match with the rule inspection criteria. If you
* specify All
, WAF inspects both keys and values.
The parts of the headers to match with the rule inspection criteria. If you
* specify All
, WAF inspects both keys and values.
What WAF should do if the headers of the request are more numerous or larger * than WAF can inspect. WAF does not support inspecting the entire contents of * request headers when they exceed 8 KB (8192 bytes) or 200 total headers. The * underlying host service forwards a maximum of 200 headers and at most 8 KB of * header contents to WAF.
The options for oversize handling are the * following:
CONTINUE
- Inspect the available
* headers normally, according to the rule inspection criteria.
* MATCH
- Treat the web request as matching the rule statement. WAF
* applies the rule action to the request.
NO_MATCH
* - Treat the web request as not matching the rule statement.
What WAF should do if the headers of the request are more numerous or larger * than WAF can inspect. WAF does not support inspecting the entire contents of * request headers when they exceed 8 KB (8192 bytes) or 200 total headers. The * underlying host service forwards a maximum of 200 headers and at most 8 KB of * header contents to WAF.
The options for oversize handling are the * following:
CONTINUE
- Inspect the available
* headers normally, according to the rule inspection criteria.
* MATCH
- Treat the web request as matching the rule statement. WAF
* applies the rule action to the request.
NO_MATCH
* - Treat the web request as not matching the rule statement.
What WAF should do if the headers of the request are more numerous or larger * than WAF can inspect. WAF does not support inspecting the entire contents of * request headers when they exceed 8 KB (8192 bytes) or 200 total headers. The * underlying host service forwards a maximum of 200 headers and at most 8 KB of * header contents to WAF.
The options for oversize handling are the * following:
CONTINUE
- Inspect the available
* headers normally, according to the rule inspection criteria.
* MATCH
- Treat the web request as matching the rule statement. WAF
* applies the rule action to the request.
NO_MATCH
* - Treat the web request as not matching the rule statement.
What WAF should do if the headers of the request are more numerous or larger * than WAF can inspect. WAF does not support inspecting the entire contents of * request headers when they exceed 8 KB (8192 bytes) or 200 total headers. The * underlying host service forwards a maximum of 200 headers and at most 8 KB of * header contents to WAF.
The options for oversize handling are the * following:
CONTINUE
- Inspect the available
* headers normally, according to the rule inspection criteria.
* MATCH
- Treat the web request as matching the rule statement. WAF
* applies the rule action to the request.
NO_MATCH
* - Treat the web request as not matching the rule statement.
What WAF should do if the headers of the request are more numerous or larger * than WAF can inspect. WAF does not support inspecting the entire contents of * request headers when they exceed 8 KB (8192 bytes) or 200 total headers. The * underlying host service forwards a maximum of 200 headers and at most 8 KB of * header contents to WAF.
The options for oversize handling are the * following:
CONTINUE
- Inspect the available
* headers normally, according to the rule inspection criteria.
* MATCH
- Treat the web request as matching the rule statement. WAF
* applies the rule action to the request.
NO_MATCH
* - Treat the web request as not matching the rule statement.
What WAF should do if the headers of the request are more numerous or larger * than WAF can inspect. WAF does not support inspecting the entire contents of * request headers when they exceed 8 KB (8192 bytes) or 200 total headers. The * underlying host service forwards a maximum of 200 headers and at most 8 KB of * header contents to WAF.
The options for oversize handling are the * following:
CONTINUE
- Inspect the available
* headers normally, according to the rule inspection criteria.
* MATCH
- Treat the web request as matching the rule statement. WAF
* applies the rule action to the request.
NO_MATCH
* - Treat the web request as not matching the rule statement.