On 15.07.2011 12:48, Lataxes, Karl wrote: > Our servlet assigns a session id to a client when it initially contacts the > server. The session id consists of "session-id", a unique client identifier, > and the current time in milliseconds, which is used as session identification > for subsequent requests. There are numerous message exchanges between the > servlet and client during a typical session, all of which contain the session > id. Once the session has successfully ended, the session id is removed from > the servlet. > > Is there any way we can configure mod_jk to recognize the session id in order > to route subsequent messages to the original Tomcat node it initially > contacted?
How does the client present the session id as part of the requests? Query parameter, path info, request header, cookie, ...? Can you five a complete example? Regards, Rainer --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
