SharePoint gives the ability to create site collections with its own domain name while the web application has a different domain name, these site collections are called hostname site collections and their creation and behavior are different from regular path-based site collections which by default are created under http:\/\/sp2010\/SITES\/XYZ\/. Below are 10 differences that I could gather which lays out the difference between hostname site collections and path-based site collections.<\/p>\n
1. SharePoint 2010 Support<\/strong> 2. DNS Support <\/strong> Path-Based Site Collection: Will to be the same as the web application<\/p>\n 3. Use of Managed Path <\/strong> Path-Based Site Collection: Yes 4. Creating Managed Path <\/strong> Path-Based Site Collection: Powershell, CA 5. Alternate Access mapping Support <\/strong> 6. Co-Exist in the same Web application <\/strong> Path-Based Site Collection: Yes<\/p>\n 7. Multiple in Single Web application<\/strong> 8. Creating site collection <\/strong> 9. Protocol Support ( HTTP\\ SSL) <\/strong> Path-Based Site Collection : 10. SSL Certificate Type <\/strong> Path-Based Site Collection : SharePoint gives the ability to create site collections with its own domain name while the web application has a different domain name, these site collections are called hostname site collections and their creation and behavior are different from regular path-based site collections which by default are created under http:\/\/sp2010\/SITES\/XYZ\/. Below are 10 differences that I […]<\/p>\n","protected":false},"author":4,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"post_mailing_queue_ids":[],"_links":{"self":[{"href":"https:\/\/teamwp.mydevfactory.com\/abhisek-saha\/aqltech\/wp-json\/wp\/v2\/posts\/2851"}],"collection":[{"href":"https:\/\/teamwp.mydevfactory.com\/abhisek-saha\/aqltech\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/teamwp.mydevfactory.com\/abhisek-saha\/aqltech\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/teamwp.mydevfactory.com\/abhisek-saha\/aqltech\/wp-json\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/teamwp.mydevfactory.com\/abhisek-saha\/aqltech\/wp-json\/wp\/v2\/comments?post=2851"}],"version-history":[{"count":0,"href":"https:\/\/teamwp.mydevfactory.com\/abhisek-saha\/aqltech\/wp-json\/wp\/v2\/posts\/2851\/revisions"}],"wp:attachment":[{"href":"https:\/\/teamwp.mydevfactory.com\/abhisek-saha\/aqltech\/wp-json\/wp\/v2\/media?parent=2851"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/teamwp.mydevfactory.com\/abhisek-saha\/aqltech\/wp-json\/wp\/v2\/categories?post=2851"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/teamwp.mydevfactory.com\/abhisek-saha\/aqltech\/wp-json\/wp\/v2\/tags?post=2851"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
\nHost-Header Site Collection: Yes
\nPath-Based Site Collection: Yes<\/p>\n
\nHost-Header Site Collection: Unique DNS name for each site collection i.e. www.customer1.com, www.customer2.com or *.customer1.com <\/p>\n
\nHost-Header Site Collection: Yes
\n\u2022 Host-Header Managed paths are different from Path-based managed paths and cannot be used for each other.
\n\u2022 Managed paths created for host-named site collections are available to all host-named site collections within the farm regardless of which Web application the host-named site collection is in.<\/p>\n
\n\u2022 Host-Header Managed paths cannot be used for Path-based site collections and Vice versa<\/p>\n
\nHost-Header Site Collection: Powershell
\nNew-SPManagedPath pathname \u2013HostHeader<\/p>\n
\nNew-SPManagedPath \u201cTeams\u201d -WebApplication \u201chttp:\/\/somestuff\u201d<\/p>\n
\nHost-Header Site Collection: No, since they are always in the same Default zone.
\nPath-Based Site Collection: Yes. And so supports multiple host header URL of its Web application using AAM<\/p>\n
\nHost-Header Site Collection: Yes
\n\u2022 As long as the host header bindings on the IIS Web site is not assigned to the Default zone of the Web application.
\n\u2022 Host header bindings in the IIS Web site can be applied to other zones of the Web application, this way Default zone will be used for host-named site collections allowing path-based site collections in other zones making use of alternate access mapping functionality.<\/p>\n
\nHost-Header Site Collection: Yes
\nPath-Based Site Collection: Yes<\/p>\n
\nHost-Header Site Collection: PowerShell
\nNew-SPSite http:\/\/www.contoso.com -OwnerAlias DOMAIN\\username – HostHeaderWebApplication http:\/\/servername\/
\nAbove command creates a site collection with the URL www.contoso.com under the web application http:\/\/servername
\nPath-Based Site Collection: PowerShell, Central Admin
\nNew-SPSite http:\/\/sitename\/sites\/test -OwnerAlias “DOMAIN\\JDoe”
\nAbove command creates path site collection under the web application<\/p>\n
\nHost-Header Site Collection :
\n\u2022 Support one at a time either HTTP or SSL depending on the Default zone of the Web application under which it is created.
\n\u2022 Need to create another web application with the default zone being https to have site collection as HTTPS <\/p>\n
\nSupports both simultaneously since it\u2019s web application can support multiple SSL certificates Each path-based site collection shares the same certificate assigned to the web application.<\/p>\n
\nHost-Header Site Collection :
\n\u2022 Only Wildcard certs ( applies to a subdomain of the same domain) and Subject Alternate Name Certs(protects multiple hostnames with a single SSL cert) can be used.
\n\u2022 Cannot apply multiple SSL to a unique domain, need to create a different web application for each then. <\/p>\n
\nCert are based on Web application and not site collection. All certs that can be applied to the web application applies to the site collection.<\/p>\n","protected":false},"excerpt":{"rendered":"