> > Do a “ping” and verify the hostnames are resolving to the correct IP. > > Then hit each http:// and https:// hostname in turn. >
You've led me to the answer! I can ping the domain with and without www. IIS is never reached for http requests as nothing is logged for them. I didn't ask my cat this time, I sat back and looked around, and I noticed the D-Link switch hanging on the wall. What if it wasn't forwarding port 80!! ... *And it wasn't* (and it hasn't for a few years, just 443). Bingo, now the http-to-https redirect is hit and it's all working as I hoped. Thanks everyone for your help. I think this problem is caused by wearing too many hats. I code for 6 hours straight and then try to do something completely unrelated which I haven't touched for a year. Modern software development is like maintaining a working atomic clock in your spare time. *GK*
