|
Problem(Abstract) |
The RewriteSetCookieDomain directive is supported in the
following minimum release levels: 4.0.2.48, 5.0.2.25, 5.1.1.1, 6.0.1.0.
Use of this directive in earlier release levels can result in a core
dump. |
|
|
|
Cause |
Some applications or servers set the domain option in the
Set-Cookie header in the response. If the domain name is the same as the
external (proxy) domain name, the configuration works correctly. However,
in some companies, the internal domain name might not be the same as the
external domain name. In this case, when the Set-Cookie header returns to
the browser, the browser is not able to forward the cookie defined in the
header because the domain name in the Set-Cookie header cannot be matched
using the external domain name. |
|
|
Resolving the
problem |
Use the RewriteSetCookieDomain directive to rewrite the
domain name value in the Set-Cookie header. This directive maps the
internal domain name to the external domain name.
Syntax:
RewriteSetCookieDomain internal-domain-pattern
external-domain-pattern
Example:
RewriteSetCookieDomain .InternalDomain.com .ExternalDomain.com |
|
|
|
|
Cross Reference information |
Segment |
Product |
Component |
Platform |
Version |
Edition |
Application Servers |
WebSphere Edge Server |
Caching Proxy |
Multi-Platform |
Edge Server 2.0 PTF2 |
|
Application Servers |
Runtimes for Java Technology |
Java SDK |
|
|
|
|
|
|