Hello, I think you had a better chance to get an answer in application thread.
I do not use tomcat at all, but as I remember, some of my friend said that it is not recommended to use tomcat web capability but to proxy through apache which is more secured. and there are a lot of doc how to use ssl in apache.
The port attribute (default value is 8443) is the TCP/IP port number on which Tomcat will listen for secure connections. You can change this to any port number you wish (such as to the default port for https communications, which is 443). However, special setup (outside the scope of this document) is necessary to run Tomcat on port numbers lower than 1024 on many operating systems.
If you change the port number here, you should also change the value specified for the redirectPort attribute on the non-SSL connector. This allows Tomcat to automatically redirect users who attempt to access a page with a security constraint specifying that SSL is required, as required by the Servlet Specification.
as I understand you have changed default https port but didn’t change redirectPort. Logically if you’ll change it then it should work.
Yes , as I can see non-SSL connector is this on port 8009. The second ssl enabled connector in your configuration is on port 81. So sounds logically to put in non-SSL connector redirectPort=81.
However documentation do not recommend to use in tomcat ports lower than 1024:
The port attribute (default value is 8443) is the TCP/IP port number on which Tomcat will listen for secure connections. You can change this to any port number you wish (such as to the default port for https communications, which is 443). However, special setup (outside the scope of this document) is necessary to run Tomcat on port numbers lower than 1024 on many operating systems.