On Tue, May 12, 2015 at 11:51 AM, Rafael Fonseca <rsafons...@gmail.com> wrote:
> I guess the rationale behind putting it on 8080 is because this is the > default for tomcat :) > Also, by default, unprivileged accounts (non-root) are unable to listen on > ports under 1024 like 80/443 (which is the reason of tomcat shipping it by > default on 8080) this is easily fixable by daemonizing it (with jsvc for > example, like it's already done for debian packaging). > Another simple workaround i usually use for this, is to have iptables > redirect port 80 to 8080 seamlessly, this allows the service to be > available both on port 80 and 8080 ;) > > Wido has a point though, who's putting tomcat directly on the line? Atleast in my experience we only do that for testing / lab, and IMHO we should package for production. -- Erik
