That's been really a great help.....Further can I control the length of this sessionID as I am working on a project for mobile devices and these devices dont support very long URLs.
Thanks -----Original Message----- From: Gabriel Gajdos [mailto:[EMAIL PROTECTED]] Sent: Monday, March 18, 2002 3:07 PM To: Tomcat Users List Subject: Re: URL Re-writting | Please tell me what is the default behaviour that Tomcat uses for | maintaining session i.e. using cookies or URL re-writting. and how do | switch | to a different mode i.e. from cookies how do I switch to URL rewritting. Tomcat uses non-persistent cookies (for Session ID) such as other server scripting engines do... If there is user with cookie enabled browser, everything works just fine with non-persistent cookie JSESSIONID... If there is not possible to use cookies, Tomcat automaticaly uses URL rewriting... At the server side, you should allways use method response.encodeURL(String url) which returns correct form for URL as needed! It means, all <A>, <FORM action=...> and similar links must be retrieved from this method... As far as I know, it is not possible to switch URL-rewriting and using cookie. I have not found any purpose to use this behaviour yet (except testing). You are just allways using response.encodeURL() and you do not need to care whether client is using cookies or not. You do not really need to care about that as a WebApp developper. GG -- To unsubscribe: <mailto:[EMAIL PROTECTED]> For additional commands: <mailto:[EMAIL PROTECTED]> Troubles with the list: <mailto:[EMAIL PROTECTED]> -- To unsubscribe: <mailto:[EMAIL PROTECTED]> For additional commands: <mailto:[EMAIL PROTECTED]> Troubles with the list: <mailto:[EMAIL PROTECTED]>