/* * 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.wafv2.model; import java.io.Serializable; import javax.annotation.Generated; import com.amazonaws.protocol.StructuredPojo; import com.amazonaws.protocol.ProtocolMarshaller; /** *
* 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
.
*
* 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.
*
* 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.
*
* 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.
*
* 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.
*
* 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.
*