On Thu, 2007-03-29 at 09:43 +0100, Pid wrote: > > They don't go through it automatically, as the links are in the page > output, and tomcat doesn't hunt through output streams for URLs to encode. > > All URLs need to be manually encoded, in your JSPs or Servlet outputs. > Check with your developers to ensure that this is the case. > > If the URLs are properly encoded Tomcat will then rewrite the URL to > include the session data in the URL if cookies are not available. > > Your URLs will then look something like: > /path/to.jsp;jsessionid=XXXXXXXX?query=goes+here
This and the addCookie worked perfectly. The developers are working on a fix right now. > The HTTPD is largely agnostic of the sessions - unless you are > clustering - as it won't interfere with a cookie, and will pass a URL > parameter through as normal. > > Q: How have you connected HTTPD/Tomcat, and which versions are you using? Tomcat 2.2.23 Apache httpd 2.2.0 mod_jk 1.2.15 > > If you *are* clustering then you need to ensure that the jvmRoute > attribute of the Engine in conf/server.xml is set uniquely for each > Tomcat. (http://tomcat.apache.org/tomcat-5.5-doc/config/engine.html) > > This adds the value of the attribute to the end of the jsessionid so > that your load balancer can direct the session to the appropriate Tomcat. No clusters yet, though we will be looking into it as soon as I learn a bit more. Thanks a lot Christopher, Pid and Nicholas, your help was very valuable. --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
