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
