/**
* Copyright Amazon.com, Inc. or its affiliates. All Rights Reserved.
* SPDX-License-Identifier: Apache-2.0.
*/
#pragma once
#include Inspect a string containing the list of the request's header names, ordered
* as they appear in the web request that WAF receives for inspection. WAF
* generates the string and then uses that as the field to match component in its
* inspection. WAF separates the header names in the string using colons and no
* added spaces, for example
* host:user-agent:accept:authorization:referer
.See
* Also:
AWS
* API Reference
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.