...
Right-click on a server in the Virtualize Server view and choose Add Message Proxy.
Right-click on a server in the SOAtest Server view and choose Add Message Proxy.
Right-click on a server in the Virtualize or SOAtest Server view and choose Add Message Proxy.
...
- Click Add Listener and choose Reverse Proxy from the Type menu.
- Specify a name for the listener.
- Click Add Port and enter a port number. You can enable the message proxy to automatically assign a port by specifying
0
as the port number. When the proxy is enabled, the assigned port number will appear in the console. The port is randomly assigned every time the message proxy is changed/enabled. You can also send a GET request to themessageProxies
API endpoint to return the automatically assigned port number. See Creating and Modifying Assets Testing through the REST API for additional information. - If the client sends traffic over SSL, enable the Secure option and enable your verification options. See SSL Settings for HTTP Reverse Listener Ports for details.
- Click OK to exit the port editor.
- Click Add to add additional ports to the listener or OK again to finish adding the listener.
...
Scroll pdf ignore | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
Configuring an HTTP Message Proxy Video TutorialThis video describes how to set up a message proxy that can capture live traffic.
|
More on Recording Session Options
Anchor | ||||
---|---|---|---|---|
|
...
If your proxies and/or Message Forward tools inadvertently set up a forwarding cycle like A> B> C> A, this could result in an infinite loop. To prevent such loops, Virtualize is configured to stop forwarding after 10 hops. To prevent such loops, SOAtest is configured to stop forwarding after 10 hops. To prevent such loops, Virtualize and SOAtest are configured to stop forwarding after 10 hops. You can change this by setting the system property parasoft.proxy.loop.max.limit
(for example, parasoft.proxy.loop.max.limit=5
).
...