We have a legacy ASP.NET webforms .aspx web application installed under “Default Web Site”.
Is it possible to enable https: for just this web application, given that there are other web applications deployed under “Default Web Site”?
All the instructions I found online insist upon creating a https: binding in IIS on port :443
The challenge is, I want to know are there any other possible ways to enable https: for just that one web application without impacting the other applications?
Assuming you are using IIS, the certificate is tied to the IP/Port binding, which is tied to the website; Default Web Site in your case.
If having a certificate on the site will break applications on the single IIS Site you’re using, I would split the applications out to their own sites.
Just having the port and cert on the site doesn’t force the site and subsequent apps to use the port and cert so, really, you should be fine.