Re: http and https on port80
From: x y (x@y.com)
Date: 11/11/02
- Next message: James Bloomer: "Bypass NTLM and Redirct user to a page"
- Previous message: scott: "Re: Websites on server 'In Error' ??"
- In reply to: Tim Greene: "Re: http and https on port80"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
From: "x y" <x@y.com> Date: Mon, 11 Nov 2002 08:54:07 -0800
... you could also have your firewall do NAT and/or PAT so
that the website appears to all be running on the same
port to the clients outside the firewall, even though it's
not.
>-----Original Message-----
>More specifically, both HTTP and HTTPS are application
layer protocols that
>use TCP as their transport, and you can't have those
application layer
>protocols connecting over the same IP/port combination.
The only way to
>have HTTP and HTTPS on the same port is to create two
sites with different
>IP addresses: 1 IP address for HTTP over port 80, and
another IP address
>for HTTPS over port 80. Naturally, you would have to
have separate DNS
>entries for those sites as well, like www.microsoft.com
and
>secure.microsoft.com.
>
>Sincerely,
>
>Tim Greene MCSE, MCSA, MCP+I
>IIS Newsgroup Support
>
>Please do not send email directly to this alias. This is
our online account
>name for newsgroup participation only.
>
>If you would like to open a support incident with
Microsoft, call
>1-800-936-5800
>
>This posting is provided "AS IS" with no warranties, and
confers no rights.
>You assume all risk for your use. © 2001 Microsoft
Corporation.
>
>.
>
- Next message: James Bloomer: "Bypass NTLM and Redirct user to a page"
- Previous message: scott: "Re: Websites on server 'In Error' ??"
- In reply to: Tim Greene: "Re: http and https on port80"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
|