On Fri, Feb 12, 2016 at 10:53:12AM -0700, George Sexton wrote: > > On 2/11/2016 11:30 AM, m...@kimwana.com wrote: > >On Thu, Feb 11, 2016 at 12:28:40PM -0500, Christopher Schultz wrote: > >>-----BEGIN PGP SIGNED MESSAGE----- > >>Hash: SHA1 > >> > >>Msh, > >> > >>On 2/10/16 7:04 PM, m...@kimwana.com wrote: > >>>I have the fillowing problem to solve for a job interview. > >A few thoughts: > > > >(1) There is no (stated) requirement that the non-secure web service > >be listening on port 80. There is no (stated) requirement that the > >secure web service be listening on port 443. Perhaps you could > >simplify things by not worrying about traditional port numbers for > >HTTP and HTTPS. > >Yeah. It took me a while to remember that http protocol can run on any > >practically any non-reserved port. > >Of course browsers expect port 80 so I added a rule in my iptables config > > > >-A PREROUTING -i eth0 -p tcp -m tcp --dport 80 -j REDIRECT --to-ports 8443 > > You can also use JSVC which will allow you to bind to reserved > ports. There are some other advantages to JSVC as well. For example, > in some cases, if the JVM fails, it can perform a re-start.
I guess a lot of folks use Apache httpd as a proxy for Tomcat. I don't even know what JSVC is. Heh! I've worked in several Tomcat shops but there were always load balancers handling such duties. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
