Go 4 Sharepoint

Search:

Welcome: Guest!

MOSS Forum

Home » Forum » MOSS

Ask a question

RSS Feeds

Define Managed Paths - Excluded Paths

Asked By: Stephanie Wilson Date: Aug 27, 2006 Category: MOSS Views: 1261

In SPS 2003, if you wanted to have a traditional file path on your
SharePoint server host non-SharePoint pages and scripts (and not use the
SharePoint ISAPI filtering) the mechanism was to use Define Managed
Paths in Central Administration, and add the URL as an excluded path.

In MOSS 2007, I've noticed that Define Managed Paths only has options to
list Included paths as URLs.

What is the mechanism, then, in MOSS 2007, to add a path that you do not
want to use ISAPI filtering? If I want to have a legacy .aspx form run
on the same server as my SharePoint front end web server, how would I go
about doing that?

Tagged:define managed paths excluded

1 Answer Found

Answer #1 Answered By: Isidro Berger Answered On: Aug 27, 2006

First, there's no ISAPI filter in WSSv3/MOSS... everything is implemented with
HTTP handlers & modules.

Second, you don't have to exclude anything... by default, v3 treats paths the
exact opposite as v2 did. So if you add a folder and a page in your web root, it
will work. Just know that if you drop a folder in there that is also the same
name as a web, I'm pretty sure your folder will win and the SharePoint web won't
be shown.

Didn't find what you were looking for? Find more on Define Managed Paths - Excluded Paths Or get search suggestion and latest updates.