> 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 scheme="https"). 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. I guess we were side tracked by the write up as it seemed to be well researched. Thanks again, Gautam --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
