Oh, that's a good point. I actually have an EchoSservlet to test stuff like this and the JSESSIONID is being passed back in that case. I've copied it's process method which is called by doGet/doPost.
LiveHTTPHeader output: http://localhost:8080/webkell/echo GET /webkell/echo HTTP/1.1 Host: localhost:8080 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.14) Gecko/20080404 Firefox/2.0.0.14 Accept: text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 Accept-Language: en-us,en;q=0.5 Accept-Encoding: gzip,deflate Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7 Keep-Alive: 300 Connection: keep-alive HTTP/1.x 200 OK Server: Apache-Coyote/1.1 Set-Cookie: JSESSIONID=C190519696B6307CE7B04F53ACC890A6; Path=/webkell Content-Length: 13 Date: Wed, 23 Apr 2008 21:23:44 GMT EchoServlet.process: public void process(HttpServletRequest req, HttpServletResponse resp) throws ServletException { com.interrupt.bookkeeping.ISystem system = (com.interrupt.bookkeeping.ISystem)req.getSession().getAttribute("system"); PrintWriter pwriter = null; try { //... printing debug stuff pwriter = new PrintWriter(resp.getOutputStream()); if(system == null) { pwriter.println("system NULL"); system = (com.interrupt.bookkeeping.ISystem)com.interrupt.bob.base.Bob.loadS( Bkell.class.getResourceAsStream("/bookkeeping.system.xml"), "xml/bookkeeping.system.xml" ); } else { pwriter.println(system.toXML(false)); } req.getSession().setAttribute("system", system); pwriter.close(); } catch(IOException e) { e.printStackTrace(); } } ----- Original Message ---- From: Christopher Schultz <[EMAIL PROTECTED]> To: Tomcat Users List <users@tomcat.apache.org> Sent: Wednesday, April 23, 2008 1:58:03 PM Subject: Re: Tomcat not sending JSESSIONID (servlet session cookie) with new sessions -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Timothy, Timothy Washington wrote: | Yes, the client and server are both on my localhost (I also tried | 127.0.0.1), and that is the requesting/sending url. Hmmm, I tried | setting that specific header (resp.addHeader("my-custom-header", | "foo");), but there's no indication it's sending(from | RequestDumpervalse output) or receiving(from LiveHTTPHeaders output) | that header value. That's totally weird. Can you duplicate the offending servlet/action/JSP/whatever and start removing things from it until it works? - -chris __________________________________________________________________ Be smarter than spam. See how smart SpamGuard is at giving junk email the boot with the All-new Yahoo! Mail. Click on Options in Mail and switch to New Mail today or register for free at http://mail.yahoo.ca
