We run Tomcat on 8080 using Cisco Routers for port redirection. Nobody has to type in a port number.
On Friday 06 February 2004 07:11 pm, you wrote: > > You can have any port be the default http port. It doesn't have to be 80. > > > > If you change /etc/services and just tell tomcat or apache to listen on > > something else, it still works fine, and people don't have to remember > > the port. > > > > Right? > > Daniel > > All true since no port number has to mean anything. But I've yet to see > any actively used production web site that didn't use 80/443 because those > are the ONLY ONES that can be reached without specifying a port number in > the URL. Considering the fact that absolutely nobody in the > non-development world ever types in a URL with a port number, you can rest > assured that no production web site relies on non-standardized port > numbers. > > Then when you consider firewalls, the ability for many sites to reach > non-standard ports gets worse because many well-secured networks block > outgoing connections to arbitrary IP+ports. Allowing outgoing connections > to be made to port 80 is common, but others are typically blocked (even > spyware and virus-introduced backdoors often use port 80 just for that > reason, even though the other end is not necessarily a web site). > > So you can use any port number you want, even ones assigned to other > systems like DNS or SMTP, but the expected behavior won't occur. > > David > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
