In Tomcat 3.3, "noCookies" controls how the session ID is handled,
i.e. forces ";jsessionid=" instead of a cookie for session tracking.
I believe this is true for Tomcat 3.2.x as well. I'm not certain
if the "cookie" Context attribute applies only to session handling.
Cheers,
Larry
> -----Original Message-----
> From: Hans Schmid [mailto:[EMAIL PROTECTED]]
> Sent: Monday, August 20, 2001 1:50 PM
> To: Tomcat-User
> Subject: Per webapp Cookies in TC3.3-b1 ?
>
>
> Hi,
>
> I need the ability to turn on Cookies in one webapp and turn
> them off in
> another.
>
> We are using Tomcat 3.3b1.
>
>
> I found the following in the Archives about Tomcat 3.2 vs Tomcat 4:
> http://www.mail-archive.com/tomcat-dev@jakarta.apache.org/msg0
9535.html
>
>In 3.2, look in "conf/server.xml" for the string
>
> noCookies="false"
>
>and change it to
>
> noCookies="true"
>
>IIRC, this change is global to all webapps in this JVM.
>
>In 4.0, the <Context> element includes a "cookies" attribute that you can
>use to turn cookies on or off on a per-webapp basis. It defaults to
>"true", so turn them off like this:
>
> <Context path="/examples" ... cookies="false" ...>
>
So is it supported in Tomcat 3.3-b1 ?
If not is it planned or do I need to upgrade to Tomcat 4 to get this
feature?
Thanks for your Help.
Best Regards,
Hans Schmid
einsurance Agency AG
Information Technology
Bayerstraße 33
80335 München
Tel: +49-89-55292- 860
Fax: +49-89-55292- 855
eMail: [EMAIL PROTECTED]
http://www.einsurance.de
