Seems like you could just add a servlet filter over the "non-sticky" servlet to invalidate the session. However if you do that, then the session is invalid, for all servlets. Is that what you want? Or do you just don't want the session cookie to be returned from the "non-sticky" servlet? That too could be done easily enough with a servlet filter.
-- Joakim Erdfelt <[email protected]> www.webtide.com Developer advice, services and support from the Jetty & CometD experts. On Wed, Aug 8, 2012 at 9:34 AM, Evan Ruff <[email protected]>wrote: > Hey guys, > > I've been working on a Jetty based project and I was hoping someone could > clarify what I'm working on. > > So the application itself is going to be behind a Layer7 Load > Balancer that will sick the sessions. I have two servlets, one that needs > to be sticky, and one that CANNOT be sticky. I was wondering if there was a > way to configure this in the servlet code to handle the conditions? Can I > invalidate the session somehow on my non-sticky servlet? > > Thanks! > > E > > _______________________________________________ > jetty-users mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/jetty-users > >
_______________________________________________ jetty-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/jetty-users
