...
- To specify the URL for the target application: choose Custom from the menu and enter the full URL, comprising of the service host, service port, and (optionally) forward path in the URL field field. See the notes below regarding each of these components of the service URL. Note that query parameters will be ignored if specified in the URL field; enter full URLs only.
- Service host: If you want the proxy to forward to a virtual asset on the local server without consuming an HTTP connection, enter
host.virt.internal,localhost, or127.0.0.1as the service host rather than the actual hostname. When usinglocalhostor127.0.0.1, the service port must match the port Virtualize is deployed on; when usinghost.virt.internalthe service port is not used. For example, a virtual asset deployed onhttp://localhost:9080/myVirtualAssetcan also be reached usinghttp://host.virt.internal/myVirtualAsset. - Service port: This is the port to which the proxy will send messages.
- Forward path: If no forward path is specified, the Proxy listen path is used. If the HTTP proxy is sending messages to localhost, you must specify a forward path because the proxy doesn't allow forwarding to itself. If the forward path sends a redirect, the proxy will follow the redirect and then respond back. It will not pass the redirect back to the client. See Service Forward Path and Proxy Listen Path for more details.
- Service host: If you want the proxy to forward to a virtual asset on the local server without consuming an HTTP connection, enter
- To specify the path to a Virtual Asset or Message Proxy for the target application: choose Virtualize from the menu and enter the path to the Virtual Asset or Message Proxy in the Path field.
- To route the request to the original host requested by the client, choose Passthrough from the menu.
...