Interface Headers.Builder
- All Superinterfaces:
Buildable
,CopyableBuilder<Headers.Builder,
,Headers> SdkBuilder<Headers.Builder,
,Headers> SdkPojo
- Enclosing class:
Headers
-
Method Summary
Modifier and TypeMethodDescriptiondefault Headers.Builder
matchPattern
(Consumer<HeaderMatchPattern.Builder> matchPattern) The filter to use to identify the subset of headers to inspect in a web request.matchPattern
(HeaderMatchPattern matchPattern) The filter to use to identify the subset of headers to inspect in a web request.matchScope
(String matchScope) The parts of the headers to match with the rule inspection criteria.matchScope
(MapMatchScope matchScope) The parts of the headers to match with the rule inspection criteria.oversizeHandling
(String oversizeHandling) What WAF should do if the headers of the request are more numerous or larger than WAF can inspect.oversizeHandling
(OversizeHandling oversizeHandling) What WAF should do if the headers of the request are more numerous or larger than WAF can inspect.Methods inherited from interface software.amazon.awssdk.utils.builder.CopyableBuilder
copy
Methods inherited from interface software.amazon.awssdk.utils.builder.SdkBuilder
applyMutation, build
Methods inherited from interface software.amazon.awssdk.core.SdkPojo
equalsBySdkFields, sdkFields
-
Method Details
-
matchPattern
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
, orExcludedHeaders
.Example JSON:
"MatchPattern": { "ExcludedHeaders": [ "KeyToExclude1", "KeyToExclude2" ] }
- Parameters:
matchPattern
- 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
, orExcludedHeaders
.Example JSON:
"MatchPattern": { "ExcludedHeaders": [ "KeyToExclude1", "KeyToExclude2" ] }
- Returns:
- Returns a reference to this object so that method calls can be chained together.
-
matchPattern
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
, orExcludedHeaders
.Example JSON:
This is a convenience method that creates an instance of the"MatchPattern": { "ExcludedHeaders": [ "KeyToExclude1", "KeyToExclude2" ] }
HeaderMatchPattern.Builder
avoiding the need to create one manually viaHeaderMatchPattern.builder()
.When the
Consumer
completes,SdkBuilder.build()
is called immediately and its result is passed tomatchPattern(HeaderMatchPattern)
.- Parameters:
matchPattern
- a consumer that will call methods onHeaderMatchPattern.Builder
- Returns:
- Returns a reference to this object so that method calls can be chained together.
- See Also:
-
matchScope
The parts of the headers to match with the rule inspection criteria. If you specify
ALL
, WAF inspects both keys and values.All
does not require a match to be found in the keys and a match to be found in the values. It requires a match to be found in the keys or the values or both. To require a match in the keys and in the values, use a logicalAND
statement to combine two match rules, one that inspects the keys and another that inspects the values.- Parameters:
matchScope
- The parts of the headers to match with the rule inspection criteria. If you specifyALL
, WAF inspects both keys and values.All
does not require a match to be found in the keys and a match to be found in the values. It requires a match to be found in the keys or the values or both. To require a match in the keys and in the values, use a logicalAND
statement to combine two match rules, one that inspects the keys and another that inspects the values.- Returns:
- Returns a reference to this object so that method calls can be chained together.
- See Also:
-
matchScope
The parts of the headers to match with the rule inspection criteria. If you specify
ALL
, WAF inspects both keys and values.All
does not require a match to be found in the keys and a match to be found in the values. It requires a match to be found in the keys or the values or both. To require a match in the keys and in the values, use a logicalAND
statement to combine two match rules, one that inspects the keys and another that inspects the values.- Parameters:
matchScope
- The parts of the headers to match with the rule inspection criteria. If you specifyALL
, WAF inspects both keys and values.All
does not require a match to be found in the keys and a match to be found in the values. It requires a match to be found in the keys or the values or both. To require a match in the keys and in the values, use a logicalAND
statement to combine two match rules, one that inspects the keys and another that inspects the values.- Returns:
- Returns a reference to this object so that method calls can be chained together.
- See Also:
-
oversizeHandling
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.
- Parameters:
oversizeHandling
- 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.
-
- Returns:
- Returns a reference to this object so that method calls can be chained together.
- See Also:
-
-
oversizeHandling
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.
- Parameters:
oversizeHandling
- 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.
-
- Returns:
- Returns a reference to this object so that method calls can be chained together.
- See Also:
-
-