Mark Palmer wrote: > I guessed as much. The thing is, I can see that the browser > is just never > getting the JSESSIONID cookies when accessing via Apache. > > If you access directly to Tomcat the JSESSIONID cookies come > no problem. > > I just don't get it - this implies that mod_jk2 is stripping > off the cookie > response headers, or tomcat is not producing them through the > jk connector.
I've seen something similar some time ago -- the behavior then was that if multiple cookies were being set in the server, only one cookie was actually getting sent in the HTTP response. This was reported as bug 12699 and fixed; maybe there has been a regression. Look at the bug at: http://issues.apache.org/bugzilla/show_bug.cgi?id=12699 and see if maybe it's the same situation. Have you tried reproducing the HTTP conversation using telnet? That way you can see exactly what's going on... telnet your.server.com 80 Trying 123.34.234.111... Connected to your.server.com. Escape character is '^]'. GET /your/servlet/url?with=parameters HTTP/1.1 Host: your.server.com Connection: close <------server response will show up here-----> The cookies being sent from the server will be in Set-Cookie headers. There will be multiple Set-Cookie headers, one per cookie that is sent from the server. If this is the same issue as 12699, only the last Set-Cookie header will actually be returned through mod_jk2. Cheers, bn --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
