Details
Description
A more viable solution would be to add both an HTTP and HTTPS connector in the CARGO Tomcat server XML files and add a couple of new properties (number, keystore, etc.) for this port. When the property would not be set, no HTTPS connector would be started.
Issue Links
- is related to
-
CARGO-574
Support simultaneous http and https connectors in tomcat5x
-
-
CARGO-977
HTTPS (cargo.protocol) support for Jetty 6.x, 7.x
-
- relates to
-
CARGO-1135
Allow direct configuration of SSL/TLS connector options for Tomcat 5.x, 6.x, and 7.x stand alone local configurations
-
Good point
Any patch propositions are most welcome...