CODEWITHSUNDEEP
asp.netasp.net-mvcazureazure-web-app-service
SBirthare
SBirthare

Reputation: 5137

Azure Web App Url - http (on portal) vs https (works by default)

I have been using Windows Azure to host some of our internal utility projects using Web App. When I create a new web app say "MyTestApp", the default URL created in portal will be:

"http://MyTestApp.azurewebsites.net"

Refer Image

enter image description here

However, when I click this URL, it will not open in browser. To fix it, I have to manually append "s" in the protocol to make it

"https://MyTestApp.azurewebsites.net".

I understand that by default, Azure secures the *.azurewebsites.net wildcard domain with a single SSL certificate, so the clients can access the app at

"https://appname.azurewebsites.net"

But I wondering why the portal display the non SSL URL (http). Is there a reason for that?

Update:

I tested it with Firefox too (based on suggestion in comments) and tried both hitting URL as well as Browse button. Since the URL is http, on new tab, it just say "waiting for MyTestApp..." and then "waiting for login.microsoft.com...".

enter image description here

Upvotes: 3

Views: 10993

Answers (1)

Tom Sun
Tom Sun

Reputation: 24549

However, when I click this URL, it will not open the WebApp in browser.

If we click the URL and the [Overview] table is fully loaded, then it will work correctly . We also can browse the website via click the [Browse] option.

why the portal display the non-SSL URL (http)?

This may be the topic about advantage and disadvantage of Http VS Https. Generally, one of the primary blockers for HTTPS adoption is the fact that the HTTPS protocol is slow. Here’s a very informative ServerFault thread showing just how big of a slowdown.HTTPS encrypts traffic between us and a server. It is more security than HTTP. And Azure also allow HTTPS access to our WebApp and support to enforce HTTPS on our WebApp.

Upvotes: 1

Related Questions