You can choose a Forward Proxy HTTP Listener that you defined when creating the proxy (see Creating Proxies) from the drop-down menu or add a new Forward Proxy HTTP Listener.

To add Forward Proxy HTTP Listeners from this dialog:

1. Click New.
2. Specify a name and port for the listener.
3. Click OK.

Enter the host name of the service whose traffic you want to monitor. This determines which hosts are recorded, sent to the live service, or sent to a virtual asset. 

To allow monitoring for all traffic, select "[All Hosts]" from the drop-down menu.

Enter a path that you want to monitor on the resource. This works in conjunction with what has been entered in the Host field to match incoming requests.

Wild cards are not allowed. To match all paths on the host, leave this field blank or select "[All]" from the drop-down menu.

In the event that there are multiple proxy connections configured that could match to an incoming request, the one with the combination of best host match and longest matching path is selected, with the host match being the more heavily weighted factor. For example, suppose there was an incoming target URL of "https://parabank.parasoft.com/parabank/services/bank/customers/12212" and four proxies that could match to it:

1. Host: parabank
   Path: /parabank
2. Host: parabank.parasoft
   Path: /parabank/services/bank/customers
3. Host: parabank.parasoft.com
   Path: /parabank/services_proxy
4. Host: parabank.parasoft.com
   Path: /parabank/services

In a situation like that, proxy #4 would be selected because, even though #2 has the more exact Path match, #4 has the better Host match and, unlike #3, at least a partial Path match.