Configuring the WSM using Device Manager

Example 2: Parsing the cookie

This example includes three WSM configurations using hashing or wild cards to determine which part of the following cookie to use for selecting a real server.

Cookie: sid=0123456789abcdef; name1=value1

To direct the WSM to use the entire sid cookie as a hashing key for selecting the real server, use the following virtual server and service settings.


Virtual Server setting	Description
Cookie Search = Disabled	Disabled--looks for the cookie in the HTTP header.
Cookie Name = sid	Embeds this cookie name in the server response. The WSM searches for this cookie name in subsequent requests from the same client.
Cookie Offset = 1	Tells the WSM to start searching at the 1st byte of the cookie.
Cookie Length = 16	Tells the WSM to extract the full 16 bytes.


Virtual Server Service 80 setting	Description
Persistent Binding = Cookie	Tells the WSM to look for the cookie embedded in the server response in subsequent requests from the same client.
Cookie Persistence Mode = Passive	Enables passive cookie-based persistence.

To direct the WSM to start with the 8th byte in the value and use only four bytes of the sid cookie (789a) as a hashing key for selecting the real server, change the following virtual server fields.

Cookie Offset = 8
Cookie Length = 4

To direct the WSM to use a wildcard in selecting the cookie, change the following virtual server field.

Cookie Name = ASPSESSIONID*

The WSM will look for a cookie name that starts with ASPSESSIONID. ASPSESSIONID123, ASPSESSIONID456, and ASPSESSIONID789 will all be seen by the switch as the same cookie name. If more than one cookie matches, only the first one will be used.