When you use Web Publishing Rules to publish an internal Web site, you cannot redirect the URL path to a different path on the internal Web server. Note
In this article, the path
is defined as that portion of the URL that appears between the first and the last forward slash characters (/
) in the URL.
For example, when you create a Web Publishing Rule that uses the following Destination Set
ISA Server automatically redirects the request to the internal Web server as follows, where Web01
is the name of your Web site:
Therefore, you cannot use paths to direct incoming requests to the root directory of an internal Web site. In this scenario, the Web site content must be stored in the site1
folder instead of in the root directory.
This issue occurs because ISA Server passes the original URL path unchanged to the internal Web site.
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix. Note
If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note
The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.The English version of this fix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone
tab in the Date and Time tool in Control Panel.
Date Time Version Size File name--------------------------------------------------------------------08-May-2003 21:24 3.0.1200.266 178,448 Mspadmin.exe 08-May-2003 21:23 3.0.1200.266 103,184 Msphlpr.dll 09-May-2003 00:45 1.0 19,572 Pathmappingeditor.hta08-May-2003 21:23 3.0.1200.266 391,440 W3proxy.exe 08-May-2003 21:24 3.0.1200.266 299,280 Wspsrv.exe
This hotfix permits you to remove some or all of the URL path, beginning with the first forward slash character (/), when you publish a Web site. For example, by creating a path mapping to remove the /site1
/ portion of the following URL, you can configure ISA Server to translate the following
Consider the following examples:
- When you specify a path mapping of /site1/site2/ to remove /site1/site2/ from the incoming Web request, the following URL
http://www.example.com/site1/site2/site3/is translated as:
- When you specify a path mapping of /site2/site3/ to remove /site2/site3/ from the request, the following URL
http://www.example.com/site1/site2/site3/is not correctly translated because the mapping does not locate a match starting with the first forward slash character. For example, the path mapping tries to locate /site2/ as the start of the path mapping, but the URL starts with /site1/.
After you install this hotfix, use the ISA Server Path Mapping Editor to configure the path mappings. This tool is a Hypertext Application (.hta) program that is installed in the default ISA Server installation folder (typically, C:\Program Files\Microsoft ISA Server) when you install this hotfix. You can use this tool to add path mappings for any Web Publishing Rule for stand-alone ISA servers or in ISA Server arrays. To add a path mapping, follow these steps.Note
After you install this hotfix, ISA Web Proxy Logging changes. The cs-uri
field contains the mapped data, not the original request. Important
To enable the functionality provided by this hotfix, you must install ISA Server Feature Pack 1. For information about how to obtain ISA Server Feature Pack 1, visit the following Microsoft Web site:
For information about how to obtain Service Pack 1 (SP1) for ISA Server, visit the following Web site:
Additionally, Microsoft recommends that you install Microsoft Internet Explorer 6.0 or later to support the functionality of the Path Mapping Editor.
- Create the Destination Set and Web Publishing Rule by using the ISA Management utility.
- Start the ISA Server Path Mapping Editor. To do this, run the PathMappingEditor.hta program from the ISA Server installation folder.
- In the ISA Server or Array list, click the ISA Server computer that you want to map the path on.
- In the Web Publishing Rule list, click the Web Publishing Rule that you want to configure.
Note You cannot define a path mapping for the "Default rule" Web Publishing Rule.
- Click Add to add a new path mapping.
- Type the prefix that you want to have removed from the URL path. For example, type /site1/.
Note The prefix must start with a forward slash character (/) and end with a forward slash character.
- Click OK.
- Quit the ISA Server Path Mapping Editor Tool.
Microsoft recommends that you define only one path translation for each Web Publishing Rule. In the case where you must map both /site1/
in the Path Mapping Editor Tool, create two Web Publishing Rules and related Destination Sets -- one for each path mapping that you define.
Path translation does not extend to multiple instances of the specified string. ISA Server searches for the first instance of the particular path mapping, and then replaces it. For example, when you create a path mapping of /site1/
, the following URL
is translated as follows:
The ISA Server Path Mapping Editor Tool rejects path definitions that violate the Request For Comments (RFC) 2396 path restrictions.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.