Optional
additionalAn array of additional certificates, which should be trusted as certificate authorities for upstream hosts, in addition to Node.js's built-in certificate authorities.
Each certificate should be an object with either a cert
key and a string
or buffer value containing the PEM certificate, or a certPath
key and a
string value containing the local path to the PEM certificate.
Optional
clientA mapping of hosts to client certificates to use, in the form of
{ key, cert }
objects (none, by default)
Optional
forwardingThe forwarding configuration for the passthrough rule.
This generally shouldn't be used explicitly unless you're
building rule data by hand. Instead, call thenPassThrough
to send data directly or thenForwardTo
with options to
configure traffic forwarding.
Optional
ignoreA list of hostnames for which server certificate and TLS version errors should be ignored (none, by default).
If set to 'true', HTTPS errors will be ignored for all hosts. WARNING:
Use this at your own risk. Setting this to true
can open your
application to MITM attacks and should never be used over any network
that is not completed trusted end-to-end.
Optional
lookupCustom DNS options, to allow configuration of the resolver used when forwarding requests upstream. Passing any option switches from using node's default dns.lookup function to using the cacheable-lookup module, which will cache responses.
Optional
proxyUpstream proxy configuration: pass through requests via this proxy.
If this is undefined, no proxy will be used. To configure a proxy provide either:
When using a remote client, this parameter or individual array values may be passed by reference, using the name of a rule parameter configured in the admin server.
Optional
trustDeprecated alias for additionalTrustedCAs
This defines the upstream connection parameters. These passthrough parameters are shared between both WebSocket & Request passthrough rules.