Specifying client cookie support

Web clipping portlets preserve cookies set on the server side, which means that when a Web clipping portlet fetches content from an origin server, it stores the cookies that the server sets (through the Set-Cookie HTTP header) and returns them on subsequent requests for more content. These cookies are not propagated to the client for security reasons. However, it may be necessary to propagate a client-side cookie through the portal to the origin server, such as a security cookie representing an identification.

Web clipping portlets can copy specific cookies from the client-portal conversation through to the portal-origin server conversation. Not all cookies are propagated; only cookies that are specified using a special configuration parameter are copied over. Specify what client-side cookies you need to preserve as a comma-separated list value for the ClientCookies configuration parameter. For example, if you have cookies called "uid" and "password" that you want to preserve through the Web clipping portlet, specify the following configuration parameter and value under the Portal Administration > Portlets > Manage Portlets > Modify Parameters:

ClientCookies = uid,password

Specifying client cookie support is not available in WebSphere Portal Versions 5.0 and 5.0.2. To use this functionality, download the latest Web Clipping portlet archive from the WebSphere portal catalog.

See also