I'm probably missing something here. I assume that if you run a site normally on port 80 and that if someone tries to use SSL and the site isn't bound to that, they would be redirected to 80.
Lots of assumptions right? Anyway I have a SP 2010 server running on IIS 7. Actually there are several sites on that server. At least one of the sites is running on 443, but the other site in question is only bound to 80.
The server only has 1 IP, so we use host header config for the SSL sites. When someone tries my port 80 site using 443 they get a big error page. port 80 it works fine. I would kind of expect this. site isn't bound to 443, but it is to 80.
Since the site isn't bound to 80 I would expect some kind of error but not the huge ASP error it throws.
1. When I hit that site on 443 it actually requests a log in, which it shouldn't because it's only bound to 80.
2. When I do log in then I get an ASP error page, which I would expect because that site isn't bound to 443.
I think this problem exists because we have 1 ip, a all of the site have unique hostnames/dns, but from the servers perspective, that ip does serve an ssl site, just for a different host name.
I'm not sure where I'm going with this. How do I force someone coming in on 443 to port 80 for this one URL without affecting other valid url's on this server?
Thanks,