On 16/06/2015 11:26, Maxim Neshcheret wrote: > Hi Mark > > We are using HTTP/1.1.
Then why are you expecting Tomcat to provide a "Keep-alive" header? That is not part of HTTP/1.1. Mark > > BR, > Maxim > > > From: Mark Thomas > Reply-To: Tomcat Users List > Date: Tuesday 16 June 2015 16:18 > To: Tomcat Users List > Subject: Re: TCP connections reuse > > On 16/06/2015 09:25, Maxim Neshcheret wrote: > Hi Christopher, > > > We actually found what was the problem with keep-alive. It is caused by the > fact that Tomcat didn’t specify parameters ‘Keep-Alive: timeout=60,max=100’, > in HTTP header. In this case Java uses parameters by default, ie ‘Keep-Alive: > timeout=0,max=5’ and that is why connection been closed by the client > immediately. > > > Please advise if it is possible to configure tomcat to set in Http response > header parameters ‘Keep-Alive: timeout=60,max=100’? Currently I’ve set > parameters ‘keepAliveTimeout="60000", maxKeepAliveRequests = "100"’ for > tomcat connector but response header still does not contain these values. > > That looks like the broken HTTP/1.0 keep-alive negotiation mentioned in > RFC 2068. That isn't how keep-alive works in HTTP/1.1 > > Mart > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
