Versions Compared

Old Version 4

changes.mady.by.user Robert Andelin

Saved on

compared with

New Version Current

changes.mady.by.user Robert Andelin

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Published by Scroll Versions from space FUNCTDEV and version SVC2022.1

...

Reverse Proxy

You can choose a Reverse Proxy HTTP Listener that you defined when creating the proxy (see Creating Proxies) from the drop-down menu or use the default listener.

You can also add Reverse Proxy HTTP Listeners from this dialog:

  1. Click New and specify a name for the listener.
  2. 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 the messageProxies API endpoint to return the automatically-assigned port number. See Creating and Modifying Assets through the REST API for additional information.  
  3. If the client sends traffic over SSL, enable the Secure option and enable your verification options. See SSL Settings for Reverse Proxy Listener Ports for details.
  4. Click OK to exit the port editor.
  5. Click Add to add additional ports to the proxy or OK again to finish adding the proxy.
Proxy listen path

Enter the path where the proxy should listen for incoming connections. To listen to all paths, select "[All Paths]" from the drop-down menu.

No two message proxies can have HTTP proxy connections with the same proxy path or with a path that matches an existing virtual asset’s HTTP path.

See Service Forward Path and Proxy Listen Path for more details.

Proxy URL

Displays the URL that should be given to the AUT.See Directing AUTs to Proxies for additional information.

...

Code Block
X-AUTHORIZATION
ANOTHER-HEADER
HEADER3

Example: Sending Traffic to a Virtual Asset

A proxy can also send traffic to a virtual asset. In that case, enter the host and port information for the Virtualize Server as if were just another service.

...

To send traffic to a virtual asset on a local server, you might use:

  • Service host: localhostService port: 9080 [Virtualize]
  • Service forward path: /pvapath
    Image Modified

The HTTP Reverse proxy makes no distinction between a virtual asset and an actual service. Both are configured the same way. However if the HTTP Reverse proxy is sending to localhost, you must specify Service forward path because the proxy doesn't allow forwarding to itself.

...