Node.js Proxy Configuration | Scheer PAS Documentation

The E2E Bridge supports deploying Node.js services using proxies. To use a proxy with your Node.js service, you need to add a proxies property to your package.json file.
proxiesis an array of JSON objects. You can specify one to multiple proxies per Node.js service. On deployment, the necessary proxy entries will be generated to the E2E Bridge.

[...]
"proxies": [{
        "protocol": "https",
        "port": 884,
        "path": "localhost/nodejs/helloworld",
        "targetHost": "localhost",
        "targetPort": 1337
    }]
[...]

Setting	Description	Mandatory	Values
protocol	Specify the protocol to use with this proxy.		http	Default.
protocol	Specify the protocol to use with this proxy.		https
port	Specify the proxy port.		A valid port number.
path	Specify the service path the service call should be routed to.
targetHost	Specify the target host the service call should be routed to. If not specified: The default target host for server mode installations is the hostname of the server. The default target host for workstation installations is localhost. For more information on installation modes, refer to Installation Modes and Bridge Domain. To deploy a Node.js service using proxy to an E2E Bridge, the target host must have a proxy node on the E2E Bridge proxy configuration. Refer to Managing Proxy Nodes for more information on how to create a proxy node.	optional	A fully qualified hostname.
targetPort	Specify the target port the service call should be routed to.		A valid port number.

The target protocol is HTTP and cannot be overridden.