Understand managed path in SharePoint

To put it simply, managed path is a way to tell the SharePoint system what kind of URL needs to be processed by Sharepoint, and what kind of URL does not need to be handled by Sharepoint.

Because SharePoint needs to search for pages in the database when retrieving pages, the managed path can tell SharePoint what pages to search for in the database, and what pages do not need to be searched.

 

The managed path option is different in SharePoint 2003 and SharePoint 2007.

• In 2003, the included (include) and exclude of the managed path must be specified explicitly.
• In 2007, the managed path has no exclude, and only the wildcard combination sion and explicit combination sion are available.

For example, the physical path of An ASPX page is in c: \ Inetpub \ wwwroot \ WSS \ virtualdirectories \ 80 \ yunpath \ test. aspx.

If it is in 2003, we need to create an exclude managed path, telling SharePoint that any page under \ yunpath \ does not need Sharepoint to look for pages.

In 2007, it is not that complicated. As long as you do not tell SharePoint that the yunpath is to be included, Sharepoint will use it as the exclude path.

 

The followingArticleIt helps you understand this point.

Allowing web applications to coexist with Windows SharePoint Services 2.0

Http://technet.microsoft.com/en-us/library/cc288964 (office.12). aspx

How to enable an ASP. NET application to run on a Sharepoint Virtual Server

Http://support.microsoft.com/kb/828810? & Clcid = 0x409

Reference

Http://www.cnblogs.com/awpatp/archive/2010/03/18/1688998.html