2012/4/16 Gautam <adva...@gmail.com>: > > >> Now in tomcat on server 2, we specified the following inside server.xml: > >> <Connector port="8443" maxHttpHeaderSize="8192" maxThreads="150" >> minSpareThreads="25" >> maxSpareThreads="75" enableLookups="true" acceptCount="100" >> connectionTimeout="20000" >> disableUploadTimeout="true" >> scheme="https" >> secure="false" >> SSLEnabled="true" >> proxyPort="443" >> proxyName="my_company_domain_name" >> /> > > Thanks for the thoughts to folks who commented. > > We have resolved this. > > The resolution was to remove the reference to https (sslEnabled = "true" and
The above is important > scheme="https"). I'd leave it to be scheme="https" Have you read the docs? Specifically: the "HTTP connectors" page in the "Configuration Reference Guide". It should explain all attributes there. > The http service then worked as designed. We also tested > the above code by adding a certificate (self signed) in tomcat. In that > instance > it also worked. > > Bottom line is if you are going reference https, then you > should have the certificate credentials in the right place. Otherwise remove > the reference and let it default to http. > The important bit is that in the Apache HTTP Server configuration that you cited above all security for HTTPS is handled by Apache HTTP Server. The traffic between Apache HTTP Server and Tomcat is plain HTTP, without any TLS. > I guess we were side tracked by the write up as it seemed to be well > researched. > Best regards, Konstantin Kolinko --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
