Tomcat does support url rewriting, but the developer must have written the
web app to support it - otherwise no dice.
-----Original Message-----
From: Filip Hanik [mailto:[EMAIL PROTECTED]]
Sent: Friday, April 13, 2001 4:05 PM
To: [EMAIL PROTECTED]
Subject: RE: URGENT - Session stickyness lost with cookies disabled
there are only two ways of tracking sessions
1. cookies
2. url rewriting
I don't know that tomcat supports (2)
Filip
~
Namaste - I bow to the divine in you
~
Filip Hanik
Software Architect
[EMAIL PROTECTED]
www.filip.net
> -----Original Message-----
> From: Tim O'Neil [mailto:[EMAIL PROTECTED]]
> Sent: Friday, April 13, 2001 1:02 PM
> To: [EMAIL PROTECTED]
> Subject: Re: URGENT - Session stickyness lost with cookies disabled
>
>
> At 12:54 PM 4/13/2001 -0700, you wrote:
> >I have configured apache for load balancing between 2 unix servers and it
> >is working fine when cookies are enabled. The requests are load balanced
> >between
> >the 2 servers and session stickyness works fine (once the session is
> >established
> >the request is always routed to the right app server based on the suffix
> >in the jsessionid).
> >
> >But when the cookies are disabled (I am encoding encoding the url) the
> >requests are
> >distributed between server1 and server2 meaning doesn't stick to
> the same
> >app server.
> >When there is a request from the browser (and the URL has the
> >jsessionid.suffix) the
> >mod_jserv doesn't route it to the right app server based on the
> suffix in
> >the jsessionid
> >and the session is lost (a new session id is created).
>
> Wouldn't you necessarily have to have cookies
> enabled to get this to work since http is a
> stateless protocol? I mean, what your asking
> the protocol to do is something it can't do
> without cookies, or something that it can use
> to record session information.
>
>
>
>
