What I think the issue is, is that the SSL Cert uses the FQDN of the host (hostname,domain.ext). The original setting is only using the hostname, which would tend to throw an SSL error indicating that there is a FQDN mismatch between the cert and URL.
So the rule adding .company.com works for the http site but not the https site. This is what I can't figure out.
Dan McFadden
You are getting double tapped by the top rule.
Or, change the rule that takes the hostname (http://site1/web1) only and push it to http not https, then let the other rule push to https. And place the http to https rule 2nd in the list, so the rewrite rules are processed in a more logical order.
I changed the top rule, the one that adds the .company.com, to redirect to http instead of https but that didn't change anything. My second rule is already the http to https rule so I didn't need to change that . However http://site1/web1 is still redirecting to https://site1.company.com/web1 but the https version of this same url is still not redirecting at all.
Dan McFadden
One more try:
on the FQDN rule: remove the stopProcessing="true", this will allow the rule to process any additional rewrite rules on the site.
Dan
Tom Grindrod
ASKER
Thanks. I'll give this a shot off hours tonight and see if there is a change.
This line:
Should be:
Open in new window
What I think the issue is, is that the SSL Cert uses the FQDN of the host (hostname,domain.ext). The original setting is only using the hostname, which would tend to throw an SSL error indicating that there is a FQDN mismatch between the cert and URL.
HTTP_HOST is not the FQDN of the site.
Dan