Previous Topic: Single Session Cookie EnforcementNext Topic: Determining Correct Settings


Enabling Wildcard Cookie Names

The following parameters are available for the Active Response configured on the Policy server. You may add these parameters to the configuration settings already selected.

COOKIE

The value for COOKIE may end in an asterisk (*). This syntax is used to indicate that any cookies beginning with that name should be considered potential foreign session cookies. If this functionality is used, the parameters COOKIEPATH and COOKIEDOMAIN are used to determine how to destroy the incoming cookies.

COOKIEPATH

This parameter is not required when you use wildcard syntax for the COOKIE parameter; its setting depends upon the session cookie. It has the following format

COOKIEPATH=<PATH for outbound cookies or cookies>

Example: COOKIEPATH=/

Default: /

COOKIEDOMAIN

This argument is optional when using wildcard syntax for the COOKIE parameter, its setting depending upon the session cookie. It has the following format:

COOKIEDOMAIN=<domain name for outbound cookie or cookies>

Example: COOKIEDOMAIN=.ca.com

Default: Blank – causes cookie to be associated with the individual web server.

A typical setting might be the following:

<@ lib=”npssessionlinker” func=”Config” 
param= ”COOKIE=APPSESSION_*;
BLOT;URL=/SneakyAttack.asp;
COOKIEDOMAIN=.mydomain.com;COOKIEPATH=/myapp/” @>