Hi Chris, Thanks for the response! However, I think what I am experiencing and what you are saying are at odds.
I have native installed, but it is the wrong version and doesn't work with my tomcat. So, essentially, it's not installed. (Unless the new protocol I am using just doesn't use the problem areas of native.) When I switched to the configuration shown, it worked. I assume it's not using native because of the trouble I had before. So, are you sure I need native with the config I show? Thanks a lot! Blake On Sat, Mar 25, 2023 at 12:54 PM Christopher Schultz < ch...@christopherschultz.net> wrote: > Blake, > > On 3/25/23 10:16, Blake McBride wrote: > > I wanted to confirm my suspicions regarding packages needed in tomcat to > > support HTTPS. > > You don't need anything except the core Tomcat and a reasonably recent > JVM to support HTTPS. You may have some other requirements you'd like to > place on top of that, but you haven't mentioned what those might be. > > > The config I am using is: > > > > <Connector port="443" > > > > protocol="org.apache.coyote.http11.Http11Nio2Protocol" > > > > sslImplementationName="org.apache.tomcat.util.net > .openssl.OpenSSLImplementation" > > ... > > > > > > My suspicion is: > > > > OpenSSL - needed > > APR - needed > > Tomcat-native - not needed > > > > Is that correct? > > No, Tomcat native contains the glue you need to get at OpenSSL, so you > need all of those things. > > You may not need OpenSSL and therefore that whole stack. Do you need > particularly high-performance TLS? > > -chris > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > >
