https://bz.apache.org/bugzilla/show_bug.cgi?id=57665
--- Comment #22 from Michael Osipov <micha...@apache.org> --- Here is possible use case: > <Service name="Catalina"> > <Connector address="localhost" port="8081" connectionTimeout="20000" > maxHttpHeaderSize="24576" redirectPort="8444" maxThreads="250" > /> > > <Connector port="8444" connectionTimeout="20000" > maxHttpHeaderSize="24576" maxThreads="250" > SSLEnabled="true" scheme="https" secure="true" > defaultSSLHostConfigName="blnn719x.ad001.siemens.net"> > <SSLHostConfig hostName="blnn719x.ad001.siemens.net" > protocols="TLSv1.2" > honorCipherOrder="true" > ciphers="HIGH:!aNULL:!eNULL:!EXPORT:!DES:!RC4:!3DES:!MD5:!PSK:!DSS"> > <Certificate > certificateFile="/etc/ssl/blnn719x.ad001.siemens.net/cert/public.pem" > > certificateKeyFile="/etc/ssl/blnn719x.ad001.siemens.net/key/private.pem" > type="RSA" /> > </SSLHostConfig> > </Connector> > > <Engine name="Catalina" defaultHost="blnn719x.ad001.siemens.net"> > <Host name="blnn719x.ad001.siemens.net" appBase="webapps" > unpackWARs="true" autoDeploy="true"> > <Valve > className="org.apache.catalina.valves.RemoteIpValve" > protocolHeader="X-Forwarded-Proto" /> > </Host> > </Engine> > </Service> > Tomcat is serving the stuff itself via HTTPS while the Apache Webserver on the same host has another hostname. Traffic might go to localhost or blnn719x.ad001.siemens.net. I don't see a reason not to support it. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
