Body (AWS SDK for Java

java.lang.Object
- com.amazonaws.services.wafv2.model.Body

All Implemented Interfaces:

StructuredPojo, Serializable, Cloneable
```
@Generated(value="com.amazonaws:aws-java-sdk-code-generator")
public class Body
extends Object
implements Serializable, Cloneable, StructuredPojo
```
Inspect the body of the web request. The body immediately follows the request headers.

This is used to indicate the web request component to inspect, in the FieldToMatch specification.

See Also:

AWS API Documentation, Serialized Form

Constructor Summary

Constructors
Constructor and Description

Body()

Constructors
Constructor and Description
`Body()`

Method Summary

All Methods Instance Methods Concrete Methods
Modifier and Type	Method and Description
`Body`	`clone()`
`boolean`	`equals(Object obj)`
`String`	`getOversizeHandling()` What WAF should do if the body is larger than WAF can inspect.
`int`	`hashCode()`
`void`	`marshall(ProtocolMarshaller protocolMarshaller)` Marshalls this structured data using the given `ProtocolMarshaller`.
`void`	`setOversizeHandling(String oversizeHandling)` What WAF should do if the body is larger than WAF can inspect.
`String`	`toString()` Returns a string representation of this object.
`Body`	`withOversizeHandling(OversizeHandling oversizeHandling)` What WAF should do if the body is larger than WAF can inspect.
`Body`	`withOversizeHandling(String oversizeHandling)` What WAF should do if the body is larger than WAF can inspect.

Methods inherited from class java.lang.Object
getClass, notify, notifyAll, wait, wait, wait

- Constructor Detail
  - Body
```
public Body()
```
- Method Detail
  - setOversizeHandling
```
public void setOversizeHandling(String oversizeHandling)
```
    What WAF should do if the body is larger than WAF can inspect.
    
    WAF does not support inspecting the entire contents of the web request body if the body exceeds the limit for the resource type. When a web request body is larger than the limit, the underlying host service only forwards the contents that are within the limit to WAF for inspection.
    - For Application Load Balancer and AppSync, the limit is fixed at 8 KB (8,192 bytes).
    - For CloudFront, API Gateway, Amazon Cognito, App Runner, and Verified Access, the default limit is 16 KB (16,384 bytes), and you can increase the limit for each resource type in the web ACL AssociationConfig, for additional processing fees.
    The options for oversize handling are the following:
    - CONTINUE - Inspect the available body contents 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.
    You can combine the MATCH or NO_MATCH settings for oversize handling with your rule and web ACL action settings, so that you block any request whose body is over the limit.
    
    Default: CONTINUE
    Parameters:
    oversizeHandling - What WAF should do if the body is larger than WAF can inspect.
    
    WAF does not support inspecting the entire contents of the web request body if the body exceeds the limit for the resource type. When a web request body is larger than the limit, the underlying host service only forwards the contents that are within the limit to WAF for inspection.
    
    For Application Load Balancer and AppSync, the limit is fixed at 8 KB (8,192 bytes).
    
    For CloudFront, API Gateway, Amazon Cognito, App Runner, and Verified Access, the default limit is 16 KB (16,384 bytes), and you can increase the limit for each resource type in the web ACL AssociationConfig, for additional processing fees.
    
    The options for oversize handling are the following:
    
    CONTINUE - Inspect the available body contents 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.
    
    You can combine the MATCH or NO_MATCH settings for oversize handling with your rule and web ACL action settings, so that you block any request whose body is over the limit.
    
    Default: CONTINUE
    See Also:
    
    OversizeHandling
  - getOversizeHandling
```
public String getOversizeHandling()
```
    What WAF should do if the body is larger than WAF can inspect.
    
    WAF does not support inspecting the entire contents of the web request body if the body exceeds the limit for the resource type. When a web request body is larger than the limit, the underlying host service only forwards the contents that are within the limit to WAF for inspection.
    - For Application Load Balancer and AppSync, the limit is fixed at 8 KB (8,192 bytes).
    - For CloudFront, API Gateway, Amazon Cognito, App Runner, and Verified Access, the default limit is 16 KB (16,384 bytes), and you can increase the limit for each resource type in the web ACL AssociationConfig, for additional processing fees.
    The options for oversize handling are the following:
    - CONTINUE - Inspect the available body contents 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.
    You can combine the MATCH or NO_MATCH settings for oversize handling with your rule and web ACL action settings, so that you block any request whose body is over the limit.
    
    Default: CONTINUE
    Returns:
    What WAF should do if the body is larger than WAF can inspect.
    
    WAF does not support inspecting the entire contents of the web request body if the body exceeds the limit for the resource type. When a web request body is larger than the limit, the underlying host service only forwards the contents that are within the limit to WAF for inspection.
    
    For Application Load Balancer and AppSync, the limit is fixed at 8 KB (8,192 bytes).
    
    For CloudFront, API Gateway, Amazon Cognito, App Runner, and Verified Access, the default limit is 16 KB (16,384 bytes), and you can increase the limit for each resource type in the web ACL AssociationConfig, for additional processing fees.
    
    The options for oversize handling are the following:
    
    CONTINUE - Inspect the available body contents 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.
    
    You can combine the MATCH or NO_MATCH settings for oversize handling with your rule and web ACL action settings, so that you block any request whose body is over the limit.
    
    Default: CONTINUE
    See Also:
    
    OversizeHandling
  - withOversizeHandling
```
public Body withOversizeHandling(String oversizeHandling)
```
    What WAF should do if the body is larger than WAF can inspect.
    
    WAF does not support inspecting the entire contents of the web request body if the body exceeds the limit for the resource type. When a web request body is larger than the limit, the underlying host service only forwards the contents that are within the limit to WAF for inspection.
    - For Application Load Balancer and AppSync, the limit is fixed at 8 KB (8,192 bytes).
    - For CloudFront, API Gateway, Amazon Cognito, App Runner, and Verified Access, the default limit is 16 KB (16,384 bytes), and you can increase the limit for each resource type in the web ACL AssociationConfig, for additional processing fees.
    The options for oversize handling are the following:
    - CONTINUE - Inspect the available body contents 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.
    You can combine the MATCH or NO_MATCH settings for oversize handling with your rule and web ACL action settings, so that you block any request whose body is over the limit.
    
    Default: CONTINUE
    Parameters:
    oversizeHandling - What WAF should do if the body is larger than WAF can inspect.
    
    WAF does not support inspecting the entire contents of the web request body if the body exceeds the limit for the resource type. When a web request body is larger than the limit, the underlying host service only forwards the contents that are within the limit to WAF for inspection.
    
    For Application Load Balancer and AppSync, the limit is fixed at 8 KB (8,192 bytes).
    
    For CloudFront, API Gateway, Amazon Cognito, App Runner, and Verified Access, the default limit is 16 KB (16,384 bytes), and you can increase the limit for each resource type in the web ACL AssociationConfig, for additional processing fees.
    
    The options for oversize handling are the following:
    
    CONTINUE - Inspect the available body contents 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.
    
    You can combine the MATCH or NO_MATCH settings for oversize handling with your rule and web ACL action settings, so that you block any request whose body is over the limit.
    
    Default: CONTINUE
    Returns:
    
    Returns a reference to this object so that method calls can be chained together.
    
    See Also:
    
    OversizeHandling
  - withOversizeHandling
```
public Body withOversizeHandling(OversizeHandling oversizeHandling)
```
    What WAF should do if the body is larger than WAF can inspect.
    
    WAF does not support inspecting the entire contents of the web request body if the body exceeds the limit for the resource type. When a web request body is larger than the limit, the underlying host service only forwards the contents that are within the limit to WAF for inspection.
    - For Application Load Balancer and AppSync, the limit is fixed at 8 KB (8,192 bytes).
    - For CloudFront, API Gateway, Amazon Cognito, App Runner, and Verified Access, the default limit is 16 KB (16,384 bytes), and you can increase the limit for each resource type in the web ACL AssociationConfig, for additional processing fees.
    The options for oversize handling are the following:
    - CONTINUE - Inspect the available body contents 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.
    You can combine the MATCH or NO_MATCH settings for oversize handling with your rule and web ACL action settings, so that you block any request whose body is over the limit.
    
    Default: CONTINUE
    Parameters:
    oversizeHandling - What WAF should do if the body is larger than WAF can inspect.
    
    WAF does not support inspecting the entire contents of the web request body if the body exceeds the limit for the resource type. When a web request body is larger than the limit, the underlying host service only forwards the contents that are within the limit to WAF for inspection.
    
    For Application Load Balancer and AppSync, the limit is fixed at 8 KB (8,192 bytes).
    
    For CloudFront, API Gateway, Amazon Cognito, App Runner, and Verified Access, the default limit is 16 KB (16,384 bytes), and you can increase the limit for each resource type in the web ACL AssociationConfig, for additional processing fees.
    
    The options for oversize handling are the following:
    
    CONTINUE - Inspect the available body contents 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.
    
    You can combine the MATCH or NO_MATCH settings for oversize handling with your rule and web ACL action settings, so that you block any request whose body is over the limit.
    
    Default: CONTINUE
    Returns:
    
    Returns a reference to this object so that method calls can be chained together.
    
    See Also:
    
    OversizeHandling
  - toString
```
public String toString()
```
    Returns a string representation of this object. This is useful for testing and debugging. Sensitive data will be redacted from this string using a placeholder value.
    
    Overrides:
    
    toString in class Object
    
    Returns:
    
    A string representation of this object.
    
    See Also:
    
    Object.toString()
  - equals
```
public boolean equals(Object obj)
```
    Overrides:
    
    equals in class Object
  - hashCode
```
public int hashCode()
```
    Overrides:
    
    hashCode in class Object
  - clone
```
public Body clone()
```
    Overrides:
    
    clone in class Object
  - marshall
```
public void marshall(ProtocolMarshaller protocolMarshaller)
```
    Description copied from interface: StructuredPojo
    
    Marshalls this structured data using the given ProtocolMarshaller.
    
    Specified by:
    
    marshall in interface StructuredPojo
    
    Parameters:
    
    protocolMarshaller - Implementation of ProtocolMarshaller used to marshall this object's data.

AWS SDK for Java 1.x API Reference - 1.12.780

Class Body

Constructor Summary

Method Summary

Methods inherited from class java.lang.Object

Constructor Detail

Body

Method Detail

setOversizeHandling

getOversizeHandling

withOversizeHandling

withOversizeHandling

toString

equals

hashCode

clone

marshall