> From: André Warnier [mailto:a...@ice-sa.com] > Subject: Re: TCP connections and HTTP sessions
> I believe it might have been in some discussion relative > to HTTP NTLM authentication You may have been looking at some discussion concerning the jCIFS NTLM filter, which has some serious problems and is scheduled to be replaced by a completely different mechanism in the next release of jCIFS. (Which is good, since the current one has no end of problems.) > To nitpick, I don't think it would influence cookies per se. Cookies > work fine even when the connection is reset and re-established, and do > not to my knowledge relate to ports (nor even in fact to IP addresses, > only to hostnames and paths). > And I am wondering how it could influence "sessions", though Because the clients would appear as just *one* client to the app server, since they're using just one TCP connection. All clientes would be sharing only one session, and all the cookies would end up on all the clients. > I guess it depends a lot on the definition of what is a session. The definition is clear from the Tomcat perspective, or from the TCP/IP perspective. As you state, the OP seemed to confuse the two. > In my understanding (and I believe Chris's), there is no such link. Agreed. Also, it didn't appear to me that the OP actually had any kind of problem... - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
