> From: Christopher Schultz [mailto:[EMAIL PROTECTED] > Subject: Re: URL rewriting For Session Tracking > > I think you are misinterpreting the OP's question... I think > he wants to /force/ the use of URL rewriting to include the > jsessionid. In that case, he /must/ run all his links through > HttpServletResponse.encodeURL.
So setting cookies="false" in the <Context> element isn't sufficient? (Assuming a session has been created via request.getSession(true), of course.) I haven't tried it, but that's the implication I got from reading the doc. What does cookies="false" actually do, then? To step back a little: why would it be important to use URL encoding to track sessions rather than do it with cookies? - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
