js script in my http://myserver.com/app1/ (please substitute cookie for 'kookie' since javaranch doesn't allow this specific js script comination)
2. returns nothing and the js equivalent to read the cookie returns null (cookie does not exist). i have searched everywhere without much luck. [ May 19, 2005: Message edited by: alan do ]
-/a<br />certified slacker...yes, my last name is 'do' - <a href="http://www.luckycouple.com" target="_blank" rel="nofollow">luckycouple.com</a>
Cookies can only be seen by the 'server' that sent them. This by default would be the context of your application, right?
can you do a kookie.setDomain("url_of_root_context")? cookies are available only to the context that set them and to all its sub-directories. so if your first app set the kookie, it would be avalable to it and all its sub-directories, but not the parent directory or any other directory.
If you do a kookie.setDomain("root_context") then the kookie will be available to all apps residing under that context.
Joined: Apr 14, 2005
neeraj, i really appreciate the reply. i am struggling with the 'domain' concept of cookies. when i specified the 'domain' when setting up the cookie, even app1 can't find it. the underlying issue may be that the 'domain' that i see isn't what its really is (as seen by the browser/cookie).
i've tried settting the cookie w/o specifying the domain and tried to read the domain information from the cookie. per the cookie specs, the 'default' domain is set if none is specified. still, i am unable to 'read' what this 'default' domain is using JSTL although i can see the value and object reference.
the domain complication MAY be due to the applications being under Tivoli Access Manager (which does redirect after authentication). if it's at all important, both applications are struts apps, running under WAS/WSAD Test Environment. thanks for any more thought anyone can give.