Hello Richard/Friends,
Maybe you could check 2 things
- the iptables to handle the incoming connections (eg: redirect
between ports and, block connections if the ip is accessing for a
specific port)
- httpd/nginx as reverse proxies for caching and other fancy stuff
Please note that I'm
On 2018-11-24 23:25, Geraldo Netto wrote:
Hello Richard/Friends,
I might be wrong, but I guess the best approach would be to use apache
httpd or nginx as a reverse proxy and leave tomcat alone
Kind Regards,
Geraldo Netto
Sapere Aude => Non dvcor, dvco
http://exdev.sf.net/
On Sun, 25 Nov
On November 24, 2018 11:05:33 PM UTC, rich...@xentu.com wrote:
>Tomcat/9.0.13
>
>
>I'd like to have my webapps generally on 443, but the manager and
>host-manager on some other port, say 444.
>
>My reason for doing that would be that I could then use linux's
>iptables
>to restrict access to 444
Hello Richard/Friends,
I might be wrong, but I guess the best approach would be to use apache
httpd or nginx as a reverse proxy and leave tomcat alone
Kind Regards,
Geraldo Netto
Sapere Aude => Non dvcor, dvco
http://exdev.sf.net/
On Sun, 25 Nov 2018 at 00:05, wrote:
>
> Tomcat/9.0.13
>
>
>
Tomcat/9.0.13
I'd like to have my webapps generally on 443, but the manager and
host-manager on some other port, say 444.
My reason for doing that would be that I could then use linux's iptables
to restrict access to 444 to a few known addresses, but anyone could
access 443.
I would of
