2015-11-03 13:16 GMT+01:00 Mark Thomas <ma...@apache.org>: > On 03/11/2015 11:36, Roel Storms wrote: > > Hello, > > > > > > I was wondering if anything special is done with cookie based session > > management in order for it to deal with HTTP pipelining. > > No. > > <snip/> > > > There are of course different scenario's that can be drawn but is there a > > way tomcat deals with this problem? > > No. > > > According to wikipedia, servers can > > easily deal with the issue of pipelining but I believe that is not the > case > > when sessions are involved. > > Tomcat supports pipelining but makes no assumptions about sessions. Keep > in mind that a proxy may be pipelining requests from different clients. > > > Is this scenario realistic? > > Yes. > > > Is it possible that two sessions exist where > > the information in the first session will be lost? > > Yes, one of those sessions is going to be lost. > > > I know by default most browsers turn pipelining off because of a lot of > > proxies and servers not supporting it. Is this one of the reasons? > > Supporting pipelining is a spec requirement so I'd be surprised if it > wasn't supported. >
I found this for the Chrome project: https://www.chromium.org/developers/design-documents/network-stack/http-pipelining No clue if other support it or not but if chrome an IE don't support I assume there are many others as well. I found that safari has support for pipelining as does Firefox but it's not enabled by default in FF. > > Session handling is certainly one reason not to use pipelining. > > Mark > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org > For additional commands, e-mail: dev-h...@tomcat.apache.org > >
