How does it work?
This criterion lets you match based on the presence of absence of a cookie name and optionally, the value.
You can select the following logical conditions:
|Value||The Rule is True When...|
|is||the cookie value you specified in the text field matches the one in the requested URL.|
|is not||The cookie value you specified in the text field does not match the one in the requested URL.|
|exists||the cookie name you specified in the text field is present in the requested URL.|
|does not exist||the cookie name you specified in the text field is not present in the requested URL.|
|is in range||the numeric cookie value is between the lower and upper bounds you selected.|
In the name field, enter the cookie name you want to use for the match.
Optionally, you can specify the value for the cookie. For a large number of values, you can paste the addresses and separate them with a space, comma, or carriage return. Any special characters should be entered the same way as the origin expects them. For example, if the origin escapes the space character as
%20, you should enter a space in this value field.
If you omit the value, the match applies to any request that contains the cookie name.
|*||matches zero or more characters||The rule includes a match where the cookie value is 123*. Some possible valid results are 123 and 123456.|
|?||matches a single character||The rule includes a match where the cookie value is 123?. Some possible valid results are 123 and 1234.|
Wildcards in name: When enabled, allows * and ? wildcard matches in the cookie name field.
Case-sensitive name: If you select this option, the cookie name in the incoming request has to match the case of the entry.
Wildcards in value: When enabled, allows * and ? wildcard matches in the value field.
Case-sensitive value: If you select this option, the value in the incoming request has to match the case of the entry.
Updated over 1 year ago