Hi,
the container will normally try to create a session cookie and then possibly
fall back on URL Rewriting if enabled. Your solution is either to instruct
the user to disable cookies. (Normally not what you want to do.) The only
other option is to hope that your container supports switching to URL
Rewriting as default. This is a configuration issue on the server. In JRun,
for instance, do service config on the servlet engine (jse), switch to the
Cookie tab and disable the option "Use session cookies".
Good luck.
Regards
/M�rten Haglind
> -----Original Message-----
> From: A mailing list about Java Server Pages specification and reference
> [mailto:[EMAIL PROTECTED]]On Behalf Of Armin Groll
> Sent: Monday, February 07, 2000 12:17 AM
> To: [EMAIL PROTECTED]
> Subject: How to avoid setting a Cookie with getSession?
>
>
> Hello,
>
> Right to the point:
>
> Does anyone know how to avoid sending a Cookie-Header when I'm getting a
> session (--> req.getSession(true);) (for use with URL-Rewriting)?
> The problem is:
> In my app, a legal person can act in different roles. Having two
> browser-windows open, he should be able to be identified as role A in
> window one and role B in window two. But the Cookies are not specific to
> the browser window, and such is there the session-id.
> I'm not keen on programming my own session-management.
>
> Thanks in advance, thanks for all the info provided before,
>
> Armin Groll
>
> ==================================================================
> =========
> To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff
> JSP-INTEREST".
> FAQs on JSP can be found at:
> http://java.sun.com/products/jsp/faq.html
> http://www.esperanto.org.nz/jsp/jspfaq.html
>
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
FAQs on JSP can be found at:
http://java.sun.com/products/jsp/faq.html
http://www.esperanto.org.nz/jsp/jspfaq.html
