Hot answers tagged

3

You can use something like this within a wrapper script that calls catalina.sh, so that future upgrades of Tomcat will not overwrite your changes. if [ "$(whoami)" != "webuser" ]; then echo "Please start this process as 'webuser'" >&2 exit 1 fi


2

Since 4.5 the Linux kernel supports the SOCK_DESTROY operation, allowing one to destroy sockets (including those connected to TCP/IP connections) e.g., with ss(8). For example here is an ssh session: $ set | grep SSH_CLIENT SSH_CLIENT='127.0.0.1 52266 22' $ Seeing the connection with ss: # ss dst 127.0.0.1:52266 Netid State Recv-Q Send-Q Local ...


2

Apache httpd added HTTP/2 support from 2.4.21 but suggest you run latest (2.4.23 at time of writing) as this module is still changing quite a bit at the moment. Tomcat has just added HTTP/2 support in Tomcat 9: https://readlearncode.com/configure-tomcat-9-for-http2/ So in theory this should all fit together nicely if you're willing to upgrade to those ...


1

You have a couple of options: Remove the out-of-the-box ROOT/ directory from tomcat and rename your war file to ROOT.war before deploying it. Deploy your war as (from your example) war_name.war and configure the context root in conf/server.xml to use your war file : <Context path="" docBase="war_name" debug="0" reloadable="true"></Context> ...


1

Use the Java keytool to create a keystore and import the certificates needed there keytool -importcert -file my_domain.cer -keystore mykeystore.jks


1

You can implement HTTP proxy, https proxy and non-http proxy also in tomcat. You need to update two files i.e, ../bin/Catalina.sh and ../conf/cataliana.properties. Detailed configuration and steps are mentioned here : http://w3devops.com/add-http-https-proxy-http-non-proxy-jenkins-via-tomcat-server/



Only top voted, non community-wiki answers of a minimum length are eligible