Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Subject: Re: Why is Tomcat sending "Connection: close?"
To: users@tomcat.apache.org
References: <B63D10721FE7744A8FC526A4D9DC3E1E71B5CFEA@MSGEXSV21136.ent.wfb.bank.corp>
From: =?UTF-8?Q?Andr=c3=a9_Warnier_=28tomcat=29?= <aw@ice-sa.com>
Message-ID: <57C6FD79.30003@ice-sa.com>
Date: Wed, 31 Aug 2016 17:53:29 +0200
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:38.0) Gecko/20100101
 Thunderbird/38.5.0
MIME-Version: 1.0
In-Reply-To: <B63D10721FE7744A8FC526A4D9DC3E1E71B5CFEA@MSGEXSV21136.ent.wfb.bank.corp>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
archived-at: Wed, 31 Aug 2016 15:54:00 -0000

On 31.08.2016 17:50, John.E.Gregg@wellsfargo.com wrote:
> All,
>
> I'm using Tomcat 7.0.70 and am having trouble understanding why Tomcat is sending "Connection: close" in the response header as often as it is.  With almost no load on the server, I get "Connection: close" pretty much every time.  The client is sending "Connection: keep-alive" but it doesn't seem to matter.  HTTP protocol is 1.1 and response code is 200.
>
> In other cases I've seen Tomcat behave exactly the way the doc says the below config should behave (100 requests per connection as long as the timeout is not exceeded) but not this time.
>
> Any idea why this is occurring or where to look to debug it?  I've tried setting breakpoints in AbstractHttp11Processor where "Connection: close" is set, but it's not hit.
>
> Thanks
>
> John
>
> Here is my connector config:
>
> <Connector port="7124"
>          protocol="HTTP/1.1"
>          SSLEnabled="true"
>          maxThreads="80"
>          maxKeepAliveRequests="100"
>          keepAliveTimeout="10000"
>          scheme="https"
>          secure="true"
>          clientAuth="true"
>          sslProtocol="TLS"
>          sslEnabledProtocols="TLSv1,TLSv1.1,TLSv1.2,SSLv2Hello,SSLv3"
>          keystoreFile="${keystoreFile}"
>          keystorePass="${keystorePassword}"
>          keyAlias="test"
>          truststoreFile="${truststoreFile}"
>          truststorePass="${truststorePassword}"
>          allowUnsafeLegacyRenegotiation="false"
>                  ciphers="SSL_DH_DSS_WITH_3DES_EDE_CBC_SHA, SSL_DHE_DSS_WITH_3DES_EDE_CBC_SHA, SSL_DHE_RSA_WITH_3DES_EDE_
> CBC_SHA, SSL_DH_RSA_WITH_3DES_EDE_CBC_SHA, SSL_RSA_WITH_3DES_EDE_CBC_SHA, SSL_RSA_WITH_RC4_128_SHA, TLS_DHE_DSS_WITH_AES
> _128_CBC_SHA, TLS_DHE_DSS_WITH_AES_256_CBC_SHA, TLS_DHE_RSA_WITH_AES_128_CBC_SHA, TLS_DHE_RSA_WITH_AES_256_CBC_SHA, TLS_
> ECDH_ECDSA_WITH_3DES_EDE_CBC_SHA, TLS_ECDH_ECDSA_WITH_AES_128_CBC_SHA, TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA, TLS_ECDHE_EC
> DSA_WITH_3DES_EDE_CBC_SHA, TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA, TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA, TLS_ECDHE_RSA_WIT
> H_3DES_EDE_CBC_SHA, TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA, TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA, TLS_ECDH_RSA_WITH_3DES_EDE_C
> BC_SHA, TLS_ECDH_RSA_WITH_AES_128_CBC_SHA, TLS_ECDH_RSA_WITH_AES_256_CBC_SHA, TLS_RSA_WITH_AES_128_CBC_SHA, TLS_RSA_WITH
> _AES_256_CBC_SHA"
>          />
>

Sorry to ask, but are you positive that there is *nothing* between the browser and Tomcat 
? (I mean like a firewall, proxy server, etc..)


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org