Microsoft Office Tutorials and References
In Depth Information
There is no short way to specify a long managed path, which should be useful
discouragement in and of itself. Remember the 260-character limit for URLs when creating paths (255
characters if you are going to do Send To for libraries or otherwise link to the path in the site).
FIGURE 10.42
Creating a new
managed path
DON’T GO MANAGED PATH CRAZY
Keep in mind that these paths are for site collections in this web application, and are available for
anyone creating a site collection, in Central Administration or via self-service. Subsite addresses
within site collections are appended to site collection addresses. This means that if you had a site
collection at http://spf2/london/sales and you wanted to create a subsite for presales projects,
you wouldn’t need to create a managed path for sales/presales to put that subsite at that address.
If you add a presales subsite to the site collection at http://spf2/london/sales, its address will
be http://spf2/london/sales/presales without additional effort.
A managed path is more than just the URL you use for site collections; it’s a critical piece
of the relationship between SharePoint and IIS; it lets IIS know what addresses to expect
SharePoint to take care of.
USING EXCLUDED PATHS
If you’d like to place a traditional website in an excluded path on the IIS server while
keeping the default port 80, you need to do a couple of things to make IIS display the site outside of
SharePoint.
For example (and I am intentionally keeping this simple), say you want the URL http://spf2/
sales/ to go to a standard website, rather than to a SharePoint site. First make certain that the site’s
path is not a managed path. T he next thing to do is place the website files in the correct location—the
root of whatever IIS Web Site is hosting port 80. As you may remember from Chapter 2, the default
site was disabled, and port 80 is used by the Web Site SharePoint-80 instead.
 
Search JabSto ::




Custom Search