The HTTP Proxy Connect profile enables a BIG-IP^® device to connect to a remote, down-stream proxy device. A client connects to the BIG-IP device, which selects a remote proxy device from a pool of proxy devices. An HTTP CONNECT handshake tells the selected remote proxy device where to connect. When the connection is established, it becomes an opaque tunnel. Any protocol can use the tunnel between the BIG-IP device and the remote proxy.

When an HTTP profile is assigned to the virtual server, the HTTP CONNECT handshake is automatically configured. If an HTTP profile not assigned to the virtual server, for example, when you have opaque SSL traffic, you can use HTTP::proxy chain iRule commands to configure the destination to which the remote proxy device routes traffic.

1. On the Main tab, click Local Traffic > Profiles > Other > HTTP Proxy Connect .
   The HTTP Proxy Connect profile list screen opens.
2. Click Create.
   The New HTTP Proxy Connect Profile screen opens.
3. In the Name field, type a unique name for the profile.
4. From the Parent Profile list, retain the default value or select another existing profile of the same type.
5. Select the Custom check box.
6. Select the Default State check box.
7. Click Finished.

1. On the Main tab, click Local Traffic > Pools .
   The Pool List screen opens.
2. Click Create.
   The New Pool screen opens.
3. In the Name field, type a unique name for the pool.
4. For the Health Monitors setting, in the Available list, select a monitor type, and click << to move the monitor to the Active list.
   Tip: Hold the Shift or Ctrl key to select more than one monitor at a time.
5. From the Load Balancing Method list, select how the system distributes traffic to members of this pool.
   The default is Round Robin.
6. For the Priority Group Activation setting, specify how to handle priority groups:
   • Select Disabled to disable priority groups. This is the default option.
   • Select Less than, and in the Available Members field type the minimum number of members that must remain available in each priority group in order for traffic to remain confined to that group.
7. Using the New Members setting, add each resource that you want to include in the pool:
   1. (Optional) In the Node Name field, type a name for the node portion of the pool member.
   2. In the Address field, type an IP address.
   3. In the Service Port field, type a port number, or select a service name from the list.
   4. (Optional) In the Priority field, type a priority number.
   5. Click Add.
8. Click Finished.

1. On the Main tab, click Local Traffic > Virtual Servers .
   The Virtual Server List screen opens.
2. Click the Create button.
   The New Virtual Server screen opens.
3. In the Name field, type a unique name for the virtual server.
4. In the Destination Address field, type the IP address in CIDR format.
   The supported format is address/prefix, where the prefix length is in bits. For example, an IPv4 address/prefix is 10.0.0.1 or 10.0.0.0/24, and an IPv6 address/prefix is ffe1::0020/64 or 2001:ed8:77b5:2:10:10:100:42/64. When you use an IPv4 address without specifying a prefix, the BIG-IP^® system automatically uses a /32 prefix.

   Note: The IP address you type must be available and not in the loopback network.
5. In the Service Port field, type a port number or select a service name from the Service Port list.
6. From the HTTP Proxy Connect Profile list, select a profile.
7. In the Resources area of the screen, from the Default Pool list, select the relevant pool name.