Edit - I answered my own question, see here → Fix the ClickJackingCheck to make sure it adds an "s" to "http" when … · umbraco/Umbraco-CMS@dc9b2b3 · GitHub
it’s a bug.
I’ll leave the question up just in case someone else sees this.
I’m running the latest version of Umbraco on Azure. I have a rule in my web.config that redirects all traffic to HTTPS.
When I run the healthcheck, everything passes except for the click-jacking protection.
Here’s the error I get
“Error pinging the URL http://sitename:443 - ‘The underlying connection was closed: An unexpected error occurred on a receive.’”
I know that http://sitename:443 returns nothing - I’ve tried with curl -i and get an empty reply. This is how it should be. Azure will not serve HTTP over 443.
My question is, why is Umbraco pinging http in the first place? It should be pinging https, right?
This is a companion discussion topic for the original entry at https://our.umbraco.com/forum/80626-healthcheck-click-jacking-protection-fails-with-an-odd-error