The HTTP Connector element represents a Connector component that supports the HTTP/1.1 protocol. It enables Catalina to function as a stand-alone web server, in addition to its ability to execute servlets and JSP pages. A particular instance of this component listens for connections on a specific TCP port number on the server. One or more such Connectors can be configured as part of a single Service, each forwarding to the associated Engine to perform request processing and create the response.
- Once all certificates have been imported into your keystore, you must edit Tomcat's configuration file to enable SSL protocol. This file is named « server.xml ». For Windows:%UserProfile% conf server.xml For Linux: /etc/tomcat7/server.xml Tomcat 7 is distributed with a pre-configured HTTPS connector. This configuration is commented.
- You would want this on an SSL Connector or a non SSL connector that is receiving data from a SSL accelerator, like a crypto card, an SSL appliance or even a webserver. The default value is false. URIEncoding: This specifies the character encoding used to decode the URI bytes, after%xx decoding the URL.
If you wish to configure the Connector that is used for connections to web servers using the AJP protocol (such as the mod_jk 1.2.x connector for Apache 1.3), please refer to the AJP Connector documentation.
I have no idea of the state of crypto on Tomcat in any version, I only know that Java's SSL/TLS implementation is in a bad state. But I can't imagine, that Java1.7 and Tomcat 7, which are part of Ubuntu 14.04, don't have too weak ciphers. Or your clients are too restrictively configured, but I assume, you haven't done that. – sebix Apr 5 '15.
Tomcat 7 Ssl Cipher Configuration
Tomcat 7 Ssl Configuration
Each incoming request requires a thread for the duration of that request. If more simultaneous requests are received than can be handled by the currently available request processing threads, additional threads will be created up to the configured maximum (the value of the maxThreads attribute). If still more simultaneous requests are received, they are stacked up inside the server socket created by the Connector, up to the configured maximum (the value of the acceptCount attribute). Any further simultaneous requests will receive 'connection refused' errors, until resources are available to process them.
