Configuring the WSM using Device Manager

About cookie-based persistence

Cookies maintain state data between clients and servers. When a server receives a client request, it issues a cookie, or token, to the client. The client returns the cookie to the server on all subsequent requests. Using cookies, the server does not require authentication, the client IP address, or any other mechanism to determine it is the same user that sent the original request. The cookie may be:

• A customer ID.
• A token of trust, allowing the user to skip authentication while his or her cookie is valid.
• A key that associates the user with additional state data that is kept on the server, such as a shopping cart and its contents.
• Encoded so that it actually contains more data than just a single key or an identification number.
• The user's preferences for a site that allows their pages to be customized.

See also:

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