Redirecting HTTP requests to HTTPS trunks
Published: January 11, 2010
Updated: February 1, 2011
Applies To: Unified Access Gateway
When you create a Forefront Unified Access Gateway (UAG) HTTPS portal trunk, only HTTPS requests that arrive at the Forefront UAG are handled by the trunk. This topic describes how to create a redirect trunk to automatically redirect HTTP requests made by remote endpoints to the HTTPS trunk.
Before you create a redirect trunk, note the following:
Make sure that you have already created the HTTPS trunk to which you want to redirect HTTP requests.
Make sure you define all the parameters of the HTTPS Connections trunk before you create the redirect trunk, including the definitions you make in the Forefront UAG Management console after completing the New Trunk Wizard.
If at a later stage, you change the IP address or port number of the HTTPS Connections trunk, do one of the following:
Update the IP address or port number manually in the relevant redirect trunk.
Delete the existing redirect trunk and create a new one.
- Update the IP address or port number manually in the relevant redirect trunk.
Redirect trunks are not monitored by the Forefront UAG Web Monitor.
Sessions in redirect trunks are not calculated in the session count of Forefront UAG. When an HTTP session is redirected to HTTPS via a redirect trunk, it is only counted as one HTTPS session.
In the Forefront UAG Management console, in the left navigation tree, right-click HTTP Connections, and then select New Trunk.
In the Create Trunk Wizard, select HTTP to HTTPS redirection, and then click Next.
All HTTPS trunks for which no redirect trunk exists are listed.
Select the HTTPS trunk to which you want to redirect HTTP requests, and then click Finish.
A new trunk with the same name as the HTTPS trunk you selected is created in the left navigation tree.
HTTP requests that arrive at the external Web site that is defined for this trunk are redirected to the HTTPS trunk you selected in the wizard.
Note: If you create a redirect trunk based on an HTTPS trunk configured in an array that does not have Forefront UAG integrated load balancing enabled (and the trunk has IP addresses assigned and activated for each array member), after creating the trunk, you must manually assign an IP address for the redirect trunk on each array member.