title: Using custom ports for SSL
body: <p>I am currently working on a strategy to migrate some of our websites/web applications to use HTTPS by default. All these applications use different host headers and are hosted on the same server. There are a number of ways of accomplishing this, but the most practical one seems to be to use a different port for every unique host header. </p>
  
  <p>My question really is: <strong>how common is to run a PUBLIC website on a custom port?</strong> What are the chances that these requests will be blocked at a local firewall or corporate proxy level? </p>
  
  <p>I used to see quite a few of these a decade ago, but they seem to have dwindled away since then, and I rarely see websites using custom ports now.  </p>