Today there was a question in StackOverflow asking whether it was possible to read the IIS binding information such as Port and Protocols from the ASP.NET application itself to try to handle redirects from HTTP to HTTPS in a way that was reliable without worrying about using different ports than 80/443.

Turns out this is possible in the context of the IIS worker process by using Microsoft.Web.Administration.

The following function will take care of that by reading the Worker Process isolated configuration file and find the HTTP based bindings.

    private static IEnumerable<KeyValuePair<string, string>> GetBindings(HttpContext context) {
        // Get the Site name 
        string siteName = System.Web.Hosting.HostingEnvironment.SiteName;

        // Get the sites section from the AppPool.config
        Microsoft.Web.Administration.ConfigurationSection sitesSection =
            Microsoft.Web.Administration.WebConfigurationManager.GetSection(null, null, "system.applicationHost/sites");
        
        foreach (Microsoft.Web.Administration.ConfigurationElement site in sitesSection.GetCollection()) {
            // Find the right Site
            if (String.Equals((string)site["name"], siteName, StringComparison.OrdinalIgnoreCase)) {

                // For each binding see if they are http based and return the port and protocol
                foreach (Microsoft.Web.Administration.ConfigurationElement binding in site.GetCollection("bindings")) {
                    string protocol = (string)binding["protocol"];
                    string bindingInfo = (string)binding["bindingInformation"];

                    if (protocol.StartsWith("http", StringComparison.OrdinalIgnoreCase)) {
                        string[] parts = bindingInfo.Split(':');
                        if (parts.Length == 3) {
                            string port = parts[1];
                            yield return new KeyValuePair<string, string>(protocol, port);
                        }
                    }
                }
            }
        }
    }

 

If you want to try it, you could use the following page, just save it as test.aspx and add the function above, the result is a simple table that shows the protocol and port to be used:

<%@ Page Language="C#" %>
<%@ Import Namespace="System.Collections.Generic" %>
<script runat="server">
    protected void Page_Load(object sender, EventArgs e) {
        Response.Write("<table border='1'>");
        foreach (KeyValuePair<string, string> binding in GetBindings(this.Context)) {
            Response.Write("<tr><td>");
            Response.Write(binding.Key);
            Response.Write("</td><td>");
            Response.Write(binding.Value);
            Response.Write("</td></tr>");
        }
        Response.Write("</table>");
    }
</script>



Also, you will need to add Microsoft.Web.Administration to your compilation assemblies inside the web.config for it to work:

<?xml version="1.0"?>
<configuration>
  <system.web>
    <compilation debug="true">
      <assemblies>
        <add assembly="Microsoft.Web.Administration, Version=7.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
      </assemblies>
    </compilation>
  </system.web>
</configuration>