|
|
|
To implement automatic domain resolution, comment out the CookieDomain parameter or set it to none to cause the Web Agent to create cookies that are good only for the server from which they were issued.
You can further define the cookie domain by adding a value to the CookieDomainScope parameter. The scope determines the number of sections, separated by periods, that make up the domain name. (A domain always begins with a ".")
A CookieDomainScope value of 0 instructs the agent to use the most specific scope for a given host. A value of 1 (resulting, for example, in a cookie domain of .com) is not allowed by the HTTP specification. The value 2 instructs the agent to use the most general scope.
The following table shows some domain names and CookieDomainScope values.
|
Domain Name |
Cookie Domain Scope value |
Cookie Domain |
|---|---|---|
|
server.myorg.com |
2 |
.myorg.com |
|
server.division.myorg.com |
3 2 |
.division.myorg.com .myorg.com |
|
server.subdivision.division.myorg.com |
4 3 2 |
.subdivision.division.myorg.com .division.myorg.com .myorg.com |
For example, the domain division.myorg.com has a scope of 3. By default, the Web Agent assumes a scope of 2; cookie domains cannot have a scope of 1.
| Copyright © 2010 CA. All rights reserved. | Email CA about this topic |