IIS subdomain redirect to HTTPS
-
So lets say I have http://xyz.bobsuncle.com and I want to redirect that to https://xyz.bobsuncle.com how would I do that with IIS's URL Rewrite?
Everything I'm seeing seems to point to
.com/somethingbut I don't care about after the .com I want to redirect from the start ensuring everyone who accessesxyz.bobsuncle.comgets forced to use SSL. -
And the reason I ask this specific question is to prevent people from just going to
xyz.bobsuncle.comwithout https.I imagine I could just disable 80 traffic entirely but that's not a part of the request.
-
It is URL rewrite. You can make complex rules just like Apache or Nginx.
https://www.namecheap.com/support/knowledgebase/article.aspx/9953/38/iis-redirect-http-to-https
-
@JaredBusch said in IIS subdomain redirect to HTTPS:
It is URL rewrite. You can make complex rules just like Apache or Nginx.
https://www.namecheap.com/support/knowledgebase/article.aspx/9953/38/iis-redirect-http-to-https
That's what I followed and it doesn't seem to work, when going to the http:// site the connection times out.
-
@DustinB3403 said in IIS subdomain redirect to HTTPS:
@JaredBusch said in IIS subdomain redirect to HTTPS:
It is URL rewrite. You can make complex rules just like Apache or Nginx.
https://www.namecheap.com/support/knowledgebase/article.aspx/9953/38/iis-redirect-http-to-https
That's what I followed and it doesn't seem to work, when going to the http:// site the connection times out.
did you check the web config and make sure it was updated?
-
@JaredBusch said in IIS subdomain redirect to HTTPS:
@DustinB3403 said in IIS subdomain redirect to HTTPS:
@JaredBusch said in IIS subdomain redirect to HTTPS:
It is URL rewrite. You can make complex rules just like Apache or Nginx.
https://www.namecheap.com/support/knowledgebase/article.aspx/9953/38/iis-redirect-http-to-https
That's what I followed and it doesn't seem to work, when going to the http:// site the connection times out.
did you check the web config and make sure it was updated?
I didn't manually check it, no.
-
I got it sorted out, the rule did work, but the firewall wasn't forwarding port 80 to the target host.
I was wondering why it worked from inside the lan, but not from the WAN. Anyways it's working now.
-
@DustinB3403 If it is not DNS, firewall is always a problem lol. Nice find.
