The only setting I know of in server.xml (or in the Context xml file) is setting cookies="false" for example:
<Context docBase="C:/dev/projects/01Practice/__source" reloadable="true" cookies="false"/> According to the definition of the cookies attribute: http://tomcat.apache.org/tomcat-6.0-doc/config/context.html "Set to true if you want cookies to be used for session identifier communication if supported by the client (this is the default). Set to false if you want to disable the use of cookies for session identifier communication, and rely only on URL rewriting by the application." After setting cookies="false" , the URL from one page to the next needs to be rewritten, so for example: <%@ page contentType="text/html;charset=UTF-8" language="java" session="true"%> <html> <head><title></title></head> <body> <% session.setAttribute("test","test"); /* Rewrite URL http://java.sun.com/javaee/5/docs/api/javax/servlet/http/HttpServletResponse.html#encodeURL(java.lang.String) */ String url = response.encodeURL("/p/test67/page2.jsp"); %> <br/><br/> <a href="<%=url%>">Go to page 2</a> </body> </html> Also disable cookies in the *browser* , when the user clicks on the above rewritten link, the jsessionid appears in the URL. I don't know if the above answers your question, but I guess it comes close. -Rashmi On 4/5/07, Kristopher Briscoe <[EMAIL PROTECTED]> wrote:
Thanks for the response. The problem is that when the wap device passes the cookie on the initial setup tomcat sees this and even though cookies are disabled - doesn't set a jsessionid. Do you know if there is a directive or config parameter I can put in server.xml that forces the creation and setting of a jsessionid even though a cookie is passed? Thanks, Kris-
--------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
