Direct Paths

The Direct Paths tool let you add virtual URLs (or paths) to your solution. Provided the path does not actually exist on your solution, the 404-handler on your IIS server will then redirect the request to the link you provided.

Please note, that if a page with the same path as the virtual URL exists, no redirect will happen (as you will not activate the 404-handler). The IIS server must be set up to resend 404 to the Dynamicweb 404-handler (Admin/Public/404.aspx).

To access the Direct Paths tool (Figure 1.1), go to Settings > Web and Http > Direct paths.

Figure 1.1 Direct Paths

To add a new direct path to your solution, click Add in the toolbar to open the Direct Path window (Figure 1.2).

Figure 1.2 Creating a new direct path

From the Direct Path window you must:

  • Provide a virtual path – e.g. news, in which case the path will be www.mydomain.com/news
  • Provide a link to redirect visitors to when they enter the direct path
  • Select the website you want the direct path to apply to
  • Select a status code for the virtual path:
    • 200 OK to keep the virtual path in the address bar
    • 301 Moved Permanently to redirect to the new URL and inform the search engine of the permanent move
    • 302 to redirect to the new URL and inform the search engine that the move is temporary. Rarely used.

You can deactivate or activate a direct path redirect using the Active checkbox.

Database

These are the database tables associated with the Direct Paths feature:

UrlPath

Contains setup data for direct paths.

Field name Data type Length
UrlPathId int 4
UrlPathPath nvarchar 255
UrlPathRedirect nvarchar 255
UrlPathStatus int 4
UrlPathCreated datetime 8
UrlPathUpdated datetime 8
UrlPathActive bit 1
UrlPathAreaId int 4
UrlPathVisitsCount int 4