Description

Match based on either the name of the request header, or on both the name of a request header and its value.

You can match based on the presence or absence of an HTTP request header and, optionally, its value. If no value is entered, any request containing the header name will produce a match.

The User-Agent and Referrer headers are commonly used for this type of match.

Cloudlets Supported

All Cloudlets support this match type.

Fields

For this match type, you complete the following fields:

Name	Description
Name	One of the standard request headers available with this match type. You can use wildcards in this field. See Available request headers for more information.
Value	The value of the request header. You can use wildcards in this field. Case sensitivity is also available for this field. In this field you have the option of pasting in a large list of values that are separated by a delimiter. Valid delimiters include tabs, and carriage returns. Note: This field is not available when the exist or does not exist operators are selected.

Wildcards

You can use wildcards with the contains any of or does not contain any of operators.

The Request Header match supports the following wildcards in the Name and Value fields:

Wildcard	Description	Example
*	matches zero or more characters	The rule includes a match where the request header value is *to . Some possible valid results for this wildcard are to, tAo, t123o**
?	matches a single character	The rule includes a match where the request header value is c?r. For this entry, cAr, or c1r are possible valid results. Some possible invalid results are: cr, caar, caaar.

Operators

This match type uses the following operators:

Value	The rule is true when	Example
`is one of`	the incoming request includes the request header and value listed in the rule’s if clause. If you select Case Sensitive, then the rule is true when the case of the characters in the value field matches that shown on the rules screen.	The rule includes a match on the From request header, where the value is jsmith, and case sensitivity hasn't been set. In this instance, any mixed case combination of the value is true, like JSmith or jSmith.
`is not one of`	the incoming request does not include the request header and value listed in the rule’s if clause. If you select Case Sensitive, then the rule is true when the case of the characters in the value field does not match that shown on the rules screen.	The rule includes a match on the From request header, where the value is jsmith, and case sensitivity hasn't been set. In this instance, any mixed case combination of the value, like JSmith or jSmith, is not valid. However, “JASmith” would be valid.
`contains any of`	the incoming request contains the request header listed in the rule’s if clause and, at minimum, the entry in the value field. If you select Case Sensitive, then the rule is true when the case of the characters in the value field matches that shown on the rules screen.	The rule includes a match on the From request header, where the value is jsmith, and case sensitivity hasn't been set. In this instance, the value in the incoming From header must, at minimum, include “jsmith” regardless of the case combination used. For example, jsmithe would be valid, but jsmit would not.
`does not contain any of`	the incoming request contains the request header listed in the rule’s if clause, and does not, in any form, include the entry listed in the value field. If you select Case Sensitive, then the rule is true when the case of the characters in the value field doesn't match that shown on the rules screen.	The rule includes a match on the From request header, where the value is jsmith, and case sensitivity hasn't been set. In this instance, the value in the incoming From header doesn't include “jsmith” regardless of the case combination used. For example, jsmit1 would be valid, but jsmith1 would not.
`exists`	the incoming request includes the request header listed in the rule’s if clause.	The rule lists the Accept request header. If the incoming request includes the Accept request header, then the rule is true.
`does not exist`	the incoming request doesn't include the request header listed in the rule’s if clause.	The rule lists the Accept request header. If the incoming request doesn't include the Accept request header, then the rule is true.

Available request headers

You can match based on any of the following request headers. You can also manually enter the names of the request header you would like to match on.

Accept
Accept-Charset
Accept-Datetime
Accept-Encoding
Accept-Language
Authorization
Cache-Control
Connection
Content-Length
Content-MD5
Content-Type
Cookie
Date
Expect
From
Host
If-Match
If-Modified-Since
If-None-Match
If-Unmodified-Since
If-Range
Max-Forwards
Origin
Pragma
Proxy-Authorization
Range
Referrer
TE
Upgrade
User-Agent
Via
Warning