Brocade Virtual ADX Server Load Balancing Guide (Supporting ADX v03.1.00) - Manual (Page 290)

274 Brocade Virtual ADX Server Load Balancing Guide
53-1003247-01
Using multiple cookies under virtual server port
5
NOTE
Spoofing can be configured with the port port number spoofing command under the virtual server
configuration.
This can also be achieved by configuring l3-default-gateway.
Configuring cookie insertion in default mode (when no CSW rule is hit)
To configure cookie insertion in default mode (when no CSW rule is hit), use the following
command.
Syntax: default rewrite insert-cookie [cookie-name [domain [path [age]]]]
The cookie-name variable specifies the name of the cookie to be inserted.
The domain variable specifies the attribute domain for the cookie to be inserted. If the domain
variable is not configured or it is configured to be "*," the default domain for the cookie inserted in
the HTTP response will be the same as the one in the previous request.
The path variable specifies the attribute path for the cookie to be inserted. If the path variable is
not configured or it is configured to be "*," then "/" is defined for the cookie path.
The age variable specifies how many minutes the browser takes to expire the cookie to be inserted.
If the age variable is not configured, the cookie will expire when the browser is closed. If the age
variable is configured to be 0, the browser will age out the cookie immediately.
NOTE
The cookie-name variable is required, while the path, domain, and age variables are optional.
Specifications
CLI commands on Brocade Virtual ADX have a limitation on the total length of each command,
When a command includes many keywords or values, the attributes of path or domain can be too
long.
The following are the internal system limitations for some attributes introduced by this command:
• cookie-name: Maximum length is 80 bytes.
• path: Maximum length is 255 bytes.
• domain: Maximum length is 80 bytes.
• age:Integer between 0 and 0x1FFFFFFF.
Configuration guidelines
Cookie insertion is typically configured together with cookie switching. If a specific cookie with valid
value is found and the associated action can be taken, the Brocade Virtual ADX will take action
based on the cookie value; otherwise, it follows other matched rules, in which possibly a cookie
insertion is triggered.
The following are the steps to configure the cookie insertion with cookie switching:
• Configure CSW rules and policy
• Bind the CSW policy to a VIP
• Enable CSW on the VIP