How does it work?
This criterion lets you match based on the presence or absence of HTTP response headers from the origin and, optionally, their value.
There are limits to what you can do with response header matches. Some features were already applied at the client request stage and you can't override them with the response settings. For example, the edge server fetches the no-store content from the origin at the request stage. That means you can't turn off a property configuration's no-store setting with a response-based match.
|Value||The Rule is True When...|
|is one of||any of the header values you specified in the text field is present in the response.|
|is not one of||any of the header values you specified in the text field is not present in the response.|
|exists||any of the header names you specified in the text field is present in the response.|
|does not exist||any of the header names you specified in the text field is not present in the response.|
|is less than||the numeric value is less than the lower bound you selected.|
|is more than||the numeric value is greater than the upper bound you selected.|
|is in range||the numeric value is between the lower and upper bounds you selected.|
In the text field, enter the name of the response header.
Optionally, you can specify the value of the header. For a large number of values, you can paste the addresses and separate them with a space, comma, or carriage return. If you omit the value, the match applies to any request that contains the parameter.
|*||matches zero or more characters||The rule includes a match where the header value is123*. Some possible valid results are 123 and 123456.|
|?||matches a single character||The rule includes a match where the header value is123?. Some possible valid results are 123 and 1234.|
Wildcards in name: When enabled, allows * and ? wildcard matches in the header name field.
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