HTTP/TCP proxy setup

The process of configuring applications to use the HTTP/TCP proxy varies according to the application.

Note: The registration.xml file, which is provided with HCL DevOps Test Virtualization Control Panel (Test Virtualization Control Panel) in the httptcp folder, includes some default settings for the HTTP/TCP proxy. You can update the configuration to work with the required applications.
You can configure the settings in a client to route HTTP and HTTPS traffic directly to the system under test, or through a proxy. Two proxy options are possible:
Standard proxy
Client requests are sent to the proxy and forwarded to the system under test. See Modifying the configuration settings of the HTTP/TCP proxy.
Reverse proxy
Client requests are forwarded according to a forward rule in the registration.xml file. See Configuring a HTTP(S) reverse proxy or TCP port forwarding.
Note: For an explanation of when to use a reverse proxy versus a standard proxy, see Virtualizing HTTP.
When an HTTPS connection is established with the HTTP/TCP proxy, the certificate that is presented to the client by the proxy is obtained by using any of the following methods:
  • Locating an existing private key and certificate that represents the intended endpoint, which is optionally loaded from the keystore file and selected based on the target hostname if available. If no matching keypair is found then a new certificate will be fabricated.
  • By using the default certificate that is generated by the proxy and signed by the private key in the keystore that is configured in registration.xml (The certificatge can either be the default greenhat one that is shipped or the one that is provided by you). Ordinarily, this mechanism is sufficient, however if full control over the generation of certificates is required then an alternative advanced approach is available that uses custom code. See Programmatic custom certificate creation in proxy.

If you are configuring an application that is already using a proxy server, you can connect the HTTP proxy to the existing proxy. See Chained proxy configuration settings.

The HTTP/TCP proxy can be used for HTTP testing, Virtualizing HTTP, testing TCP-based protocols (such as FIX, IMS™, IPIC and MQTT), and virtualizing TCP.

The following tasks are related to HTTP/TCP proxy configuration:
The following links provide instructions for configuring each listed application type to use the HTTP/TCP proxy: