>You can't have http and https listen on the same port since https has an >entire SSL handshake that must take place before the GET/POST transfer takes >place. But you could have the 8080 redirect to something like 8081 with >HTTPs running on that instead. Of course, the "correct" way is to use port >80 for http, and redirect to 443 for https, since all other ports will >really have problems for just about anybody with a firewall "correctly"
>configured. > >David Thanks for the excellent advice. Question: if you type "https://xx.xx.xx.xx/"; who is it that "knows" this goes to port 443? I have port 80 forwarded by my firewall to another machine running only Apache. Tomcat is on another machine, and I've been using port 8080 forwarded to that machine. If I type in "https://xx.xx.xx.xx/";, who knows that that should go to port 443? Is it whatever server is listening to port 80 (i.e. I then must turn on redirection in Apache), or is this a "net standard"? Thanks, -Richard -- To unsubscribe: <mailto:[EMAIL PROTECTED]> For additional commands: <mailto:[EMAIL PROTECTED]> Troubles with the list: <mailto:[EMAIL PROTECTED]>
