Share via

Configuring how to redirect HTTP requests in Web publishing

  • Article

After you create a Web publishing rule in Microsoft Forefront Threat Management Gateway, you may want to modify how HTTP requests are redirected to the published server.

To configure how to redirect HTTP requests for a Web publishing rule

  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 Bridging tab, specify whether requests will be redirected to an FTP server or to a Web server by selecting one of the following:

    • FTP server. If you select this option, in the text box, type the port on the FTP server to which the request will be redirected.
    • Web server.

  5. If you selected Web server, do the following:

    • If HTTP requests will be passed to the Web server by using the HTTP protocol, click Redirect requests to HTTP port.
    • If HTTP requests will be passed to the Web server over SSL connections, click Redirect requests to SSL port.

  6. (Optional) If you selected Redirect requests to SSL port, click Use a certificate to authenticate to the SSL Web server and click Select to select the client certificate to use.

  7. Click OK.

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

Notes

  • If you selected Redirect requests to SSL port, the Forefront TMG computer will open a new secure control channel to the published Web server.
  • When you select to redirect Web server requests to both the HTTP and SSL ports, incoming traffic is routed through the appropriate protocol and port. When you select only one option, all traffic is routed through that port.
  • If you select FTP server in step 4, Forefront TMG will not perform link translation.
  • Changes that you make to the properties of a Web publishing rule or the Web listener associated with it apply only to new connections.
  • For more information about SSL bridging, see About SSL bridging and publishing.