URL Query Parameter Wildcard

Category: URL

Purpose: Identifies requests by whether a query string parameter in the requested URL matches a pattern defined by a wildcardThis type of value supports the use of special characters to establish a pattern. For example, specifying an asterisk within this type of value will match one or more characters. value.

Key information:

• Parameter name:
  • Query parameter name comparisons are case-insensitive.
  • Replace spaces in the parameter name with %20.
  • Only query parameters whose name is an exact match to the specified value may satisfy this condition.
• Parameter value:

  • The value(s) associated with this match condition may be defined using any combination of numbers, letters, and/or symbols. This type of value also supports the use of special characters.

    Each specified value may contain one or more asterisks. Each asterisk will match a sequence of one or more characters.

  • Certain characters require URL encoding. Use the percentage symbol to URL encode the following characters:

    Character	URL Encoding
    Space	%20
    &	%26
    %	%25

  • Specify multiple query string parameter values by delimiting each one with a single space. This match condition is satisfied when a request contains one of the specified name/value combinations.

    Example 1:

    ValueA ValueB

    This configuration will match the following query string parameters:

    Parameter1=ValueA
    Parameter1=ValueB

    Example 2:

    Value%20A Value%20B

    This configuration will match the following query string parameters:

    Parameter1=Value%20A
    Parameter1=Value%20B

  • Only exact matches to at least one of the specified query string name/value combinations will satisfy this condition.

    Using the configuration in the above example, the parameter name/value combination "Parameter1=ValueAdd" would not be considered a match. However, setting the Value option to either of the following values would match that name/value combination:

    • ValueA ValueB ValueAdd
    • ValueA* ValueB
  • The case-sensitivity of header value comparisons is determined by the Ignore Case option.

  • The Result option determines the conditions under which this match condition will be satisfied.

    • Match: Requires the request to contain the specified parameter and its value must match one of the patterns defined in this match condition.

    • Does Not Match: Requires that the request satisfy either of the following criteria:

      • It does not contain the specified parameter.
      • It contains the specified parameter, but its value does not match one of the patterns defined in this match condition.

• Due to the manner in which cache settings are tracked, this match condition is incompatible with the following features:

  • Complete Cache Fill (End-of-Life)
  • Default Internal Max-Age
  • Force Internal Max-Age
  • Ignore Origin No-Cache
  • Internal Max-Stale
  • URL Rewrite

Sample Scenarios

Sample scenarios are provided below.

The following sample configurations assume that this match condition is satisfied when a request matches the specified value.

Name	Value	Result
User	Joe	This pattern will be satisfied when the query string for a requested URL is "?user=joe."
User	*	This pattern will be satisfied when the query string for a requested URL contains a "user" parameter.
Email	Joe*	This pattern will be satisfied when the query string for a requested URL contains an Email parameter that starts with "Joe."