...
| Info |
|---|
Using HTTP listeners is the recommended connection configuration for recording HTTP traffic, as it simplifies updating the client application to point to the Virtualize server’s host and HTTP listener port without requiring any changes to the paths. This applies whether forwarding traffic to a live service or a virtual asset. |
| Excerpt |
|---|
To For example, to send traffic to a virtual asset on a remote server using an HTTP listener, you could use:
To send traffic to a virtual asset on a local server using an HTTP listener, you might use:
To send traffic to a virtual asset on a remote server using an HTTP listener and fail over to a virtual asset on the local server, you could use:
When you have set both a primary and secondary connection, you can set one as the active forwarding connection and use the other as a fallback connection in case the active connection fails. You can also switch which is primary and which is secondary easily from the Server view. See HTTP Configuration for more information. To send traffic to a virtual asset on a local server without an HTTP listener, you might use:
|
...
| Tip |
|---|
If you already have your application pointing directly to a virtual asset deployed at If you already have your application pointing directly to a virtual asset and you can’t easily change the path where the AUT sends messages:
This configuration would allow you to add a proxy between your application and the virtual asset without making any changes to the AUT. |
For more information about setting up HTTP proxies, see HTTP Configuration.