Export (0) Print
Expand All
0 out of 1 rated this helpful - Rate this topic

Configuring path mappings

After you create a Web publishing rule in Microsoft Forefront Threat Management Gateway, you may want to modify the mappings of paths that may be specified in requests for the published Web site to the paths on the published Web server.

  1. In the Forefront TMG Management console tree, click Firewall Policy.

  2. In the details pane, click the applicable rule.

  3. On the Tasks tab, click Edit Selected Rule.

  4. On the Paths tab, click Add.

  5. In the text box, type a path on the published Web server (the internal path).

  6. Select one of the following:

    • Same as published folder. Select this option if the path that will be specified in requests (the external path) is identical to the internal path.
    • The following folder. Select this option if a different external path will be mapped to the internal path that you specified in step 5. Type the external path that will be mapped to the path on the published Web server.
  7. Click OK.

  8. Repeat steps 4 through 7 for each path mapping that you want to create.

  9. Click OK.

  10. In the details pane, click the Apply button to save and update the configuration, and then click OK.

Notes

  • For more information about Web publishing, see Overview of Web publishing concepts.
  • When a client makes a Web request, a path may be specified in the request. This is called the external path. Forefront TMG changes all external paths specified in a path mapping to the corresponding internal path on the Web server.
  • When you specify the internal path to which an external path should be mapped, use this format: /mypath/*.
  • You cannot use a wildcard character within a folder name. For example, do not specify mypath*/ or /mypath*.
  • Avoid specifying a file name when you configure path mapping. If a file name is specified, only a request for the full path will be served.
  • Paths must be distinct from each other. A path cannot be a prefix of another path. This is true for internal and external paths. For example, /pathA/* and /pathB/* are distinct paths. However /pathA/* is a prefix for /pathA/a/, and Forefront TMG will not allow both of those paths to be entered.
  • Forefront TMG does not treat paths as case-sensitive. If your Web server includes both foldera and folderA and you publish a path to one of the folders, both folders will be published.
  • Changes that you make to the properties of a Web publishing rule or the Web listener associated with it apply only to new connections.
Did you find this helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft. All rights reserved.