<p>I'm using IIS in Windows 2003 Server for a SharePoint intranet. <br />External incoming requests will be using the host header <code>portal.mycompany.com</code> and be forced to use SSL.</p>

<p>I was wondering if there's a way to set up an alternate host header such as <br /><code>http://internalportal/</code> <br />which only accepts requests from the internal network, but doesn't force the users to use SSL.</p>

<p>Any recommendations for how to set this up?</p>

[{'answer_id': 5505, 'author': 'Alan Hecht', 'author_id': 624, 'author_profile': 'https://Stackoverflow.com/users/624', 'pm_score': 1, 'selected': False, 'text': '<p>Assuming that <a href="http://internalportal/" rel="nofollow noreferrer">http://internalportal/</a> wasn\'t accessible from outside the company, you could set up two websites in IIS. The first site, configured to use a host header value of \'portal.mycompany.com\', would require SSL. The second site, configured to use a host header value of \'internalportal\', would not require SSL. The host header value is configured under \'Web Site\' -> \'Advanced\'.</p>\n\n<p>Having a hardware load balancer makes things much easier. The site on the load balancer is set up to require SSL, and your websites in IIS are setup not to require SSL.</p>\n'}, {'answer_id': 5585, 'author': 'Kev', 'author_id': 419, 'author_profile': 'https://Stackoverflow.com/users/419', 'pm_score': 1, 'selected': False, 'text': '<p>You could just add a second host header and internal IP address to the site for internal non-ssl access</p>\n\n<pre><code>172.16.3.1:443:portal.mycompany.com\n172.16.3.2:80:internalportal\n</code></pre>\n'}, {'answer_id': 12519, 'author': 'Daniel McPherson', 'author_id': 897, 'author_profile': 'https://Stackoverflow.com/users/897', 'pm_score': 3, 'selected': True, 'text': '<p>Daniel, keep in mind that just because something is possbile in IIS, and via any number of off box solutions (like hardware load balancers and SSL) doesn\'t mean that it is supported by SharePoint, <strong>or</strong> that it is implemented in the same way.</p>\n\n<p>You can do what you are asking for, however you should do it via SharePoint Central Administration, and "Create or Extend a Web Application" and then "Extend and Existing Application". </p>\n\n<p>In this way you can create a <strong>new</strong> web site (in IIS) for accessing your existing SharePoint Web Application, one that can be accessed via a different hostheader, port, using SSL, Authentication mechanism, etc. </p>\n\n<p>As a general rule, if you can do something in IIS AND in SharePoint, you should do it only in SharePoint.</p>\n'}]
['https://Stackoverflow.com/questions/5494', 'https://Stackoverflow.com', 'https://Stackoverflow.com/users/697/']