locked
Sharepoint Hosted Apps on Host Header based Web Applications vs Web Application without Host Header RRS feed

  • Question

  • Hi
    Experts,

    We are in process of configuring our SharePoint environment to support SharePoint Apps.


    Following is the existing set up:

    1> Couple of Web Applications that are host header based. These have different App Pool Identities
    2> SSL Offloading happens at Application Load Balancer and not at the SharePoint Server

    Since the App. Domain has to be a unique and different from the host domain, we see suggestions indicating need for a Web App. hosted on port 80 without any Host Header (http://blogs.msdn.com/b/sofocle/archive/2014/06/16/the-importance-of-the-quot-unbound-quot-web-application.aspx). This will help resolve App. URL requests which cannot be resolved by host header
    based Web Applications.

     Also. based on another the TechNet article at https://technet.microsoft.com/en-us/library/dn144963.aspx, it is possible to set up SP Apps for Host Header based Web Applications, with a few key limitations:

     - To share an app domain across two web applications, the web applications must share the same application pool identity and both have to be configured to use the same zone and authentication scheme.

    - You cannot use IIS ports that are already being used when you configure App domains.

    - If the app domain is configured to use secure sockets layer (SSL) you must configure the App domain to use a wildcard certificate and bind the SSL to a different port from the web application SSL port.

    Please share your experience in setting up the SharePoint Apps. in your environment and how you dealt with Host Header based Web Apps. Any other learning's, insights around the limitations mentioned above will be of help. It will great if you can
    as well specify details around DEV. TEST/QA and PROD environments.

    Thanks in advance.


    Thanks, Ashish Malhotra

    Thursday, March 12, 2015 7:14 PM

All replies

  • Hi Ashish,

    Please refer to the information below:

    "If you are using a host header for your web application apps won’t just work for that web application. Because of how the redirect for the app domain works IIS will try to resolve the app url by using the default IIS web site, which of course doesn’t work. If you want to use host headers for your web applications you have to create an extra web application that is listening on port 80 (or 443 if you are using https) and that doesn’t have a host header.    
    This means that you have to create a web application like you normally would. You have to make sure that you select port 80 (or 443 if you are using https) and you should not fill in a host header. Note that you have to stop the Default Web Site in IIS in order to be able to do this. The web application will use the server name as its url. The web application can be empty except for a root site collection.

    Another option is to use web applications without host headers and to create Host Header Site Collections. Be aware that Host Header Site Collections cannot be created via the user interface, they can only be created by using PowerShell."  

    From here:

    http://sharepointchick.com/archive/2012/07/29/setting-up-your-app-domain-for-sharepoint-2013.aspx 

    Or here is a article about how to set up an on-premises development environment for apps for SharePoint for your reference:

    https://msdn.microsoft.com/en-us/library/fp179923(v=office.15)

    Best Regards,

    Dennis Guo


    TechNet Community Support
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Monday, March 16, 2015 9:17 AM
  • Thanks Dennis, I had seen that link in past but I am lloking for official Microsoft guidance / documentation as we need to set up our environments correctly.

    Thanks, Ashish Malhotra

    Wednesday, March 18, 2015 3:16 PM
  • Hi, did you ever sort this out?
    Friday, June 10, 2016 9:36 AM