I've been trying to get state tracking with url rewriting to work, in the case that the client does not support or use cookies. My question is this: Does anyone know under what circumstances the servlet engine (javawebserver1.1.3 in this case) decides to include the session id in the url? (assume that the client does not use cookies) For example, my setup routes all url's throught response.encodeUrl(myUrl). It seems that the servlet implmentation looks at the String myUrl and decides whether or not to include the session id. If I run "http://localhost/servlet/myServlet?myParameter=myValue" through, the sessionID is NOT included. I assume this is because it thinks that fully qualified urls (ie ones that include the schema) are pointed away from the server. If I run "myServlet?myParameter=myValue" through, the sessionID IS included, I get "http://localhost/servlet/myServlet;$sessionid$TE4093098GHJEK093098?myParame ter=myValue", the encoded url. if "null", I get "http://localhost/servlet/;$sessionid$TE4093098GHJEK093098", which does not make much sense. Accordingly, if "mailto:[EMAIL PROTECTED]" I get " mailto:[EMAIL PROTECTED];$sessionid$TE4093098GHJEK093098, which of course is not a valid email address. So is it just the http schema that it decides not to include the session id? It seems that this implementation issue was not thought out in great detail. Any help would be greatly appreciated, Paul ___________________________________________________________________________ To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff SERVLET-INTEREST". Archives: http://archives.java.sun.com/archives/servlet-interest.html Resources: http://java.sun.com/products/servlet/external-resources.html LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
