tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From <John.E.Gr...@wellsfargo.com>
Subject RE: Why is Tomcat sending "Connection: close?"
Date Wed, 31 Aug 2016 16:50:33 GMT
No, unfortunately not.  I put "%{Connection}i %{Connection}o" in the log config and get "Keep-Alive
close."  IOW the client sends Keep-Alive but Tomcat responds with close.

Thanks




-----Original Message-----
From: André Warnier (tomcat) [mailto:aw@ice-sa.com] 
Sent: Wednesday, August 31, 2016 10:53 AM
To: users@tomcat.apache.org
Subject: Re: Why is Tomcat sending "Connection: close?"

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


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


Mime
View raw message