Class: Aws::WAFV2::Types::JsonBody

Inherits:
Struct
  • Object
show all
Defined in:
gems/aws-sdk-wafv2/lib/aws-sdk-wafv2/types.rb

Overview

Inspect the body of the web request as JSON. The body immediately follows the request headers.

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

Use the specifications in this object to indicate which parts of the JSON body to inspect using the rule's inspection criteria. WAF inspects only the parts of the JSON that result from the matches that you indicate.

Example JSON: "JsonBody": \{ "MatchPattern": \{ "All": \{\} \}, "MatchScope": "ALL" \}

Constant Summary collapse

SENSITIVE =
[]

Instance Attribute Summary collapse

Instance Attribute Details

#invalid_fallback_behaviorString

What WAF should do if it fails to completely parse the JSON body. The options are the following:

  • EVALUATE_AS_STRING - Inspect the body as plain text. WAF applies the text transformations and inspection criteria that you defined for the JSON inspection to the body text string.

  • 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.

If you don't provide this setting, WAF parses and evaluates the content only up to the first parsing failure that it encounters.

WAF does its best to parse the entire JSON body, but might be forced to stop for reasons such as invalid characters, duplicate keys, truncation, and any content whose root node isn't an object or an array.

WAF parses the JSON in the following examples as two valid key, value pairs:

  • Missing comma: \{"key1":"value1""key2":"value2"\}

  • Missing colon: \{"key1":"value1","key2""value2"\}

  • Extra colons: \{"key1"::"value1","key2""value2"\}

Returns:

  • (String)


4109
4110
4111
4112
4113
4114
4115
4116
# File 'gems/aws-sdk-wafv2/lib/aws-sdk-wafv2/types.rb', line 4109

class JsonBody < Struct.new(
  :match_pattern,
  :match_scope,
  :invalid_fallback_behavior,
  :oversize_handling)
  SENSITIVE = []
  include Aws::Structure
end

#match_patternTypes::JsonMatchPattern

The patterns to look for in the JSON body. WAF inspects the results of these pattern matches against the rule inspection criteria.



4109
4110
4111
4112
4113
4114
4115
4116
# File 'gems/aws-sdk-wafv2/lib/aws-sdk-wafv2/types.rb', line 4109

class JsonBody < Struct.new(
  :match_pattern,
  :match_scope,
  :invalid_fallback_behavior,
  :oversize_handling)
  SENSITIVE = []
  include Aws::Structure
end

#match_scopeString

The parts of the JSON to match against using the MatchPattern. If you specify ALL, WAF matches against 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 logical AND statement to combine two match rules, one that inspects the keys and another that inspects the values.

Returns:

  • (String)


4109
4110
4111
4112
4113
4114
4115
4116
# File 'gems/aws-sdk-wafv2/lib/aws-sdk-wafv2/types.rb', line 4109

class JsonBody < Struct.new(
  :match_pattern,
  :match_scope,
  :invalid_fallback_behavior,
  :oversize_handling)
  SENSITIVE = []
  include Aws::Structure
end

#oversize_handlingString

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:

  • (String)


4109
4110
4111
4112
4113
4114
4115
4116
# File 'gems/aws-sdk-wafv2/lib/aws-sdk-wafv2/types.rb', line 4109

class JsonBody < Struct.new(
  :match_pattern,
  :match_scope,
  :invalid_fallback_behavior,
  :oversize_handling)
  SENSITIVE = []
  include Aws::Structure
end