HTTP Composite
|
HTTP User
Agent, HTTP URL, HTTP Cookie and HTTP Referer flavors serve as session
parameters.
|
<HTTP User
Agent flavor, HTTP URL flavor, HTTP Cookie flavor, HTTP Referer flavor>
- The flavors can be chosen
using flavor browsing.
|
HTTP User Agent
|
HTTP User-Agent
retrieved from the HTTP <User-Agent prefix> Request header field, from
the beginning of the Request header until the first “/”.
For example, if
the HTTP Request header field is Mozilla/4.0, the HTTP User Agent retrieved is
Mozilla.
If you want to
configure the HTTP User Agent flavor with a Forward slash (/), set the value of
the GT_CLS_ENABLE_FULL_USER_AGENT_ BASED_FLAVOR_CALCULATION tunable to True.
|
<User-Agent
prefix>
Examples:
- <Moz*> matches all
HTTP sessions with User-Agent field starting with “Moz”.
- <Mozilla> matches all
HTTP sessions with User-Agent field equal to “Mozilla”.
- The maximum key length is 32
characters.
|
HTTP URL
|
- Host—Retrieved either from
the HTTP Host header field or from the Request URL. In the latter case, the
section from the beginning of the URL until the first “/” is considered the
Host.
- Path—Retrieved from the HTTP
URL, the section from the first “/” to the “?”.
- URL parameters—Any string
following the “?” (You do not need to start the params with “?”).
|
|
HTTP Cookie
|
Cookie
“Key-Value” pairs that are retrieved from the HTTP Request header Cookie field.
A Cookie may
consist of many “Key-Value” pairs; however, only the first three pairs are
calculated. The Cookie flavor calculation stops when one of the “Key-Value”
pairs matches the specification, or when it has exceeded the three pair limit.
|
<key
prefix, value prefix>
- For example:
<act*,*> matches any Cookie pair where the Key begins with “act”,
regardless of the Value.
- A flavor can be configured
so that the Value field is required to be empty. In this case, this field
should be left empty in the flavor item.
- White spaces are not
allowed, “=” is not allowed, and “*” is only allowed at the end of the Key or
Value.
- The maximum key length is
100 characters for both the Key and Value fields
|
HTTP Referer
|
Similar to HTTP
URL, but the parameters are retrieved from the Referer HTTP header field.
|
|
HTTP Content
Category
|
Content
Categories can be imported using the Import dialog box or the HTTP Content
Filtering Settings dialog box.
|
Value selected
from Select a Content Category dialog box.
|
RTSP User Agent
|
RTSP User-Agent
field that is retrieved from the RTSP message header.
|
<RTSP User
Agent prefix>
- For example: <abc*>
matches all RTSP sessions where the User-Agent starts with “abc”.
- The maximum key length is
128 characters
|
RTSP Host Name
|
RTSP Host field
that is retrieved from the RTSP message header.
|
<RTSP Host
suffix>
- For example: <*abc>
matches all RTSP sessions where the Host ends with “abc”.
- The maximum key length is
128 characters
|
RTSP Composite
|
RTSP User Agent
and RTSP Host Name flavors serve as session parameters.
|
<RTSP User
Agent flavor, RTSP Host Name flavor>
|
SIP Source
Domain
|
SIP Source Host
field that is retrieved from the SIP message header.
|
<SIP Host
suffix>
- For example: <*abc>
- The maximum key length is
128 characters
|
SIP Composite
|
SIP Source
Host and SIP Destination Host serve as session parameters.
|
<SIP
source domain, SIP destination domain>
|
SIP
Destination Domain
|
SIP
Destination Host field that is retrieved from the SIP message header.
|
<SIP Host
suffix>
- For example: <*abc>
- The maximum key length is
128 characters
|
SMTP Host
Name
|
SMTP Host
field that is retrieved from the SMTP message header
|
- <SMTP Host suffix>
- For example: <*abc>
- The maximum key length is
128 characters
|
ToS
|
DSCP value
extracted from the IP header
|
DSCP ToS
(integer from 0 through 63)
|