Sunday, February 17, 2002 07:43 PM
I'm not sure this is possible. The default port for all browsers that use "https://yourservername.com" is port 443. And servers like apache or IIS will automatically start a listener on port 443 to support HTTPS. The problem is that HTTPS is not HTTP, and therefor has traditionally run on a different listener, and a different port. What you are asking for would require HTTP and SSL/HTTPS to both be running on port 80 and I'm not sure that's ever been done. If it were to be done, the listener would have to be smart enough to know that either HTTPS or HTTP is coming and it would have to switch to that protocol during the handshake, pretty advanced stuff.
I would re-think your requirement for having them both on port 80. Besides, putting HTTPS: on port 80 would require that browsers use whacky URLs like "https://yourserver.com:80" just to tell the browser NOT to use port 443. Are you certain that you need this requirement to solve your problem?