Configuring the WSM using Device Manager

Rewrite cookie mode

The following figure illustrates the rewrite cookie mode. The WSM generates the cookie value on behalf of the server. The server is configured to return a special persistence cookie which the WSM is configured to recognize. The WSM intercepts this persistence cookie and rewrites the value to include server-specific information before sending it on to the client. Subsequent requests from the same client with the same cookie value are sent to the same real server.

Rewrite cookie mode requires at least eight bytes in the cookie header. An additional eight bytes must be reserved if you are using cookie-based persistence with Global Server Load Balancing (GSLB).

Note: Rewrite cookie mode only works for cookies defined in the HTTP header, not cookies defined in the URL.

Note: The WSM rewrites the cookie to an encoded value that represents the responding server.The value can be hashed into a real server ID or it can be the real server IP address.

See also:

• Insert cookie mode
• Passive cookie mode
• About session persistence
• Defining permanent versus temporary cookies
• Cookie formats
• Cookie properties
• Handling client browsers that do not accept cookies
• Configuring cookie-based session persistence
• Examples of cookie values
• SSL session ID-based persistence
• Configuring SSL session ID-based persistence