<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Site Collection on Matt Thornton</title>
    <link>https://matt-thornton.net/tags/site-collection/</link>
    <description>Recent content in Site Collection on Matt Thornton</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <lastBuildDate>Thu, 09 Dec 2010 13:39:03 +0000</lastBuildDate><atom:link href="https://matt-thornton.net/tags/site-collection/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Guide: MOSS 2007 Multiple site collections on Port 80</title>
      <link>https://matt-thornton.net/tech/sharepoint/guide-moss-2007-multiple-site-collections-on-port-80/</link>
      <pubDate>Thu, 09 Dec 2010 13:39:03 +0000</pubDate>
      
      <guid>https://matt-thornton.net/tech/sharepoint/guide-moss-2007-multiple-site-collections-on-port-80/</guid>
      
        <description>&lt;p&gt;Requirement: multiple site collections on port 80 on unique URLs in SharePoint 2007, e.g,. &lt;em&gt;http://democlient1&lt;/em&gt;, &lt;em&gt;http://someotherdemo&lt;/em&gt;&lt;br&gt;
The scenario: you have one development machine which you use for multiple clients. Because of this, you want to host multiple site collections and allow a unique URL for each, without having to specify the port number in the URL. For example, if your machine name is &lt;em&gt;SPDEV&lt;/em&gt; then by &lt;strong&gt;default&lt;/strong&gt; your primary web application will respond on &lt;em&gt;http://spdev&lt;/em&gt;. But you also want to have &lt;em&gt;http://democlient1&lt;/em&gt;, &lt;em&gt;http://someotherdemo&lt;/em&gt;, etc. There are a three ways of doing this. The two common ways are 1) assign unique IP addresses to each web application each responding on port 80, but this can be more complicated to setup and manage at the machine level, or 2) Use a non-standard port number for each web application, but this creates uglier URLs, e.g., &lt;em&gt;http://democlient1:18765&lt;/em&gt;, &lt;em&gt;http://someotherdemo:18734&lt;/em&gt; etc.&lt;/p&gt;
&lt;p&gt;Solution: It&amp;rsquo;s possible to achieve the requirement.&lt;/p&gt;</description>
      
    </item>
    
  </channel>
</rss>