none
Host header missing - Manual IIS binding

    Question

  • Hello All,

    I have a working environment  and need you expert opinion on this. In client environment, while creating web applications, host header value was not entered and web application was crated on port 80  , I notice that IIS bindings for some web applications were created manually, when I use the command below I see host header is coming blank, no value.

    $webapp=Get-SPWebApplication
    $b=$webapp.GetIisSettingsWithFallback("default")
    $b.ServerBindings

    Question is , Is it ok to continue using system as it is ? what could be the potential issues with this set up of "No host header with manual IIS binding" ? there is no plan to use HNSC btw . 

    I can go back, detach/reattach  the database, recreate web app with host header but since things are working fine client is hesitant to do that ?  please share your thoughts or any other possible solution.

    Thanks in advance !

    Thursday, March 30, 2017 1:36 PM

Answers

  • First, if you are using Apps (Add-ins) then one Web Application must be created with no host header.  Otherwise Apps won't work.  

    Second, the only time a host header is required would be if you create two or more Web Applications that use the same port.  In that case IIS needs a host header to figure out which traffic should go to which web site. But even in that case one of the web applications can be created with no host header.  You just can't have two without host headers.

    It should also be mentioned that the host header in the IIS bindings should match the host header recorded in the Web Application settings.


    Paul Stork SharePoint Server MVP
    Principal Architect: Blue Chip Consulting Group
    Blog: http://dontpapanic.com/blog
    Twitter: Follow @pstork
    Please remember to mark your question as "answered" if this solves your problem.


    Thursday, March 30, 2017 3:37 PM
  • 1) If you create the Web App without a host header you wouldn't add the IIS binding later.  You would leave it as being identified by just the port.

    2) You can create a second web application on the same port as long as the second web application uses a host header.  That's true whether the first web app used a host header or not.

    3) if you aren't using Apps or HNSC then you can use host headers on all your Web Applications.  If you are using either of those then you need a Web App without a host header.

    4) IIS bindings need to match whatever host header or lack of host header you are using.


    Paul Stork SharePoint Server MVP
    Principal Architect: Blue Chip Consulting Group
    Blog: http://dontpapanic.com/blog
    Twitter: Follow @pstork
    Please remember to mark your question as "answered" if this solves your problem.

    • Marked as answer by UmrG Thursday, March 30, 2017 5:10 PM
    Thursday, March 30, 2017 4:46 PM

All replies

  • First, if you are using Apps (Add-ins) then one Web Application must be created with no host header.  Otherwise Apps won't work.  

    Second, the only time a host header is required would be if you create two or more Web Applications that use the same port.  In that case IIS needs a host header to figure out which traffic should go to which web site. But even in that case one of the web applications can be created with no host header.  You just can't have two without host headers.

    It should also be mentioned that the host header in the IIS bindings should match the host header recorded in the Web Application settings.


    Paul Stork SharePoint Server MVP
    Principal Architect: Blue Chip Consulting Group
    Blog: http://dontpapanic.com/blog
    Twitter: Follow @pstork
    Please remember to mark your question as "answered" if this solves your problem.


    Thursday, March 30, 2017 3:37 PM
  • Thanks Paul for clarification. As of not no plans for apps or HNSC.

    From the answer it seems like there is no down side of  having a web application that was "created without host header and added IIS bindings later manually"  other than "second web application cannot be created on same port" . ( even thou second web app can be created on port 80 in combination with host header).

    Is that correct understanding ?

    Thanks again for quick response.

    Thursday, March 30, 2017 3:51 PM
  • 1) If you create the Web App without a host header you wouldn't add the IIS binding later.  You would leave it as being identified by just the port.

    2) You can create a second web application on the same port as long as the second web application uses a host header.  That's true whether the first web app used a host header or not.

    3) if you aren't using Apps or HNSC then you can use host headers on all your Web Applications.  If you are using either of those then you need a Web App without a host header.

    4) IIS bindings need to match whatever host header or lack of host header you are using.


    Paul Stork SharePoint Server MVP
    Principal Architect: Blue Chip Consulting Group
    Blog: http://dontpapanic.com/blog
    Twitter: Follow @pstork
    Please remember to mark your question as "answered" if this solves your problem.

    • Marked as answer by UmrG Thursday, March 30, 2017 5:10 PM
    Thursday, March 30, 2017 4:46 PM