Changed condition to Request protocol match condition
ERR_TOO_MANY_REDIRECTS in the case of Azure CDN(http-to-https redirect rule)
Getting to many redirects after creating rule:
I followed this post:
https://learn.microsoft.com/en-gb/azure/cdn/cdn-standard-rules-engine
found from this post:
https://medium.com/azure-architects/configuring-azure-cdn-http-https-redirection-2a9e4aab0a77
The UI seems to have changed... No longer have access to HTTP Large > Rules Engine through the CDN profile.
Now, the rules engine is a tab on the CDN endpoint itself, rather than the profile. I think the subscription tier causes the variance.
I created a storage acc, blob storage, enabled a static webpage, created a cdn endpoint (https://makesethmad.azureedge.net), custom domain (www.issethmad.com) pointed to the cdn endpoint successfully and HTTPS enabled through azure's provided SSL.
The goal is to make make issethmad.com and https://issethmad.com/ redirect to my correct site.
CDN endpoint with SSL enabled through Azure CDN HTTPS feature
Google Domain has cname record of www.issethmad.com that points to "https://makesethmad.azureedge.net"
DNS setting: subdomain forward from "issethmad.com" to https://makesethmad.azureedge.net
Note: https://makesethmad.azureedge.net was working with all the DNS settings. Issue flared when I added the rule, not to say my DNS settings are perfect :D
Thank you for taking time to read this!
1 additional answer
Sort by: Most helpful
-
Balaji 51 Reputation points
2023-07-21T16:21:17.8+00:00 can you please explain this error in details?
curl https://mysite.com
<html>
<head><title>308 Permanent Redirect</title></head>
<body>
<center><h1>308 Permanent Redirect</h1></center>
<hr><center>nginx</center>
</body>
</html>