Request headers do not match

Matches when any specified request header name or pattern is missing or mismatched.

This condition inspects the incoming request to verify if a specific set of header names and their corresponding values is absent. It returns true if any specified header name is missing or if any header value does not match its respective regular expression.

Configuration

  • Case sensitive: Whether to enable case sensitivity during the comparison. When disabled, the condition performs a case-insensitive match for both the header names and the values against the defined patterns.
  • Name: The exact name of the request header to inspect. Multiple headers can be added to the list.
  • Pattern: The RE2 regular expression used to evaluate the specific header’s value.
  • Defined patterns: The list of all active name-pattern pairs for this condition. The condition returns true if the request fails to match the entire set defined in this list.

Measurement

The condition resolves the specified headers from the incoming request and evaluates them against the Defined patterns as a collective set.

  • Match found: If any header value fails to match its defined pattern, the condition returns true.
  • No match found: The condition returns false only if every header name is present and every corresponding value matches its defined regular expression.
  • Missing header: If any specified header name is absent from the request, the condition returns true.

Performance

  • Sequential validation: The system must evaluate each header entry in the list until a result is determined. Processing time increases incrementally with each additional name-pattern pair defined.
  • Short-circuit optimization: The system stops processing and returns true as soon as a mismatch is identified or a missing header is detected. To minimize processing time, place the headers most likely to be missing or mismatched at the top of the list.

Last modified March 5, 2026