Versions Compared

Old Version 1

changes.mady.by.user Chieko Sugizaki

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 SVC2023.1

...

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

Tip

If you already have your application pointing directly to a virtual asset deployed at /existing, you would set the Service forward path to /existing.

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:

  1. Edit the virtual asset to prefix its path with /pva/path
  2. Deploy the proxy to /path with a forward path set to /pva/path

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 Reverse Proxy Configuration.