- Posted by: Andrea Giovannini
- Posted on: March 11 2003 11:33 EST
in my application
- the user opens a page for the first time (and some objects are stored in the web session)
- this page (in a custom tag) makes a request to a servlet
URLConnection conn = url.openConnection();
where cookie is something like "JSESSIONID=43527628366".
This works fine in Tomcat but doesn't work with Websphere 5 :-(
I can see only two options:
- my code is not standard
- Websphere bug ????
Can anybody help me to find a solution which work for both web containers?
Thank you very much in advance!!
Just as an FYI: When using WAS 3.5 a couple of years ago, we noticed the problem you mention here. We decided to use URL rewriting instead.
Note the syntax: ("Cookie", "sesessionid=4553cx987e2")
sesessionid?? May be that's the secret...
I followed your hint but that doesn't work with WAS 5.0 ....
It seems that WAS has a custom cookie management.
Still looking for the solution (possibly different from changing application server :-))
Does anybody know some good resources (other tips'n tricks like the one mentioned in srinivasan's post) ??