SizeConstraintStatement ¶

class SizeConstraintStatement(TypedDict, closed=True):
    field_to_match: "capo_wafv2.types.field_to_match.FieldToMatch"
    """<p>The part of the web request that you want WAF to inspect. </p>"""
    comparison_operator: "capo_wafv2.types.comparison_operator.ComparisonOperator"
    """<p>The operator to use to compare the request part to the size setting. </p>"""
    size: "capo_wafv2.types.size.Size"
    """<p>The size, in byte, to compare to the request part, after any transformations.</p>"""
    text_transformations: "capo_wafv2.types.text_transformations.TextTransformations"
    """<p>Text transformations eliminate some of the unusual formatting that attackers use in web requests in an effort to bypass detection. Text transformations are used in rule match statements, to transform the <code>FieldToMatch</code> request component before inspecting it, and they're used in rate-based rule statements, to transform request components before using them as custom aggregation keys. If you specify one or more transformations to apply, WAF performs all transformations on the specified content, starting from the lowest priority setting, and then uses the transformed component contents. </p>"""
    pre_parse_text_transformations: NotRequired[
        "capo_wafv2.types.pre_parse_text_transformations.PreParseTextTransformations"
    ]
    """<p>Pre-parse text transformations normalize the raw query string before WAF parses it into individual query arguments. They are applied before the standard text transformations. Pre-parse text transformations are only supported when <code>FieldToMatch</code> is <code>SingleQueryArgument</code> or <code>AllQueryArguments</code>. You can specify up to 10 pre-parse text transformations per rule statement.</p>"""