Syntax
routerIpResolver:
'$ref': <string>
errorOutcome: continue
httpClientConfig: {}
port: <int>
routerIps: <string>
ssl: {}
routerIpResolver:
'$ref': <string>
errorOutcome: continue
httpClientConfig: {}
port: <int>
routerIps: <string>
ssl: {}
Attributes
| Name | Required | Default | Description | Examples |
|---|---|---|---|---|
| $ref | false | - | Reference a component defined under components. | - |
| errorOutcome | false | ABORT | - | - |
| port | false | If not set (=0), the default port of the connection protocol (https) is used. | - | - |
| routerIps | false | - | - | - |
Child Structure
| Element | Cardinality | Description |
|---|---|---|
| httpClientConfig | 0..1 | Settings the HTTP client uses for calls to a backend: socket timeouts, an upstream proxy, credentials, TLS and retry behavior. Every part is optional and falls back to its defaults when omitted. Configure it once globally, or on a single plugin that calls a backend. |
| ssl | 0..1 | Configures a TLS context: the identity (key and certificate) presented to the peer, the certificates trusted from it, and handshake parameters such as protocol, ciphers, and client-certificate policy. Attach it to a serviceProxy/api to terminate inbound TLS, or to a target to make an outbound connection over TLS; most attributes and child elements apply to both directions, but a few - such as clientAuth and useAsDefault - only take effect on an inbound context. See tutorials/ssl-tls/10-TLS-Termination.yaml for inbound termination and tutorials/ssl-tls/20-Central-SSL-Config.yaml for sharing one ssl across several APIs via $ref. |