Gateway Server Configuration
This is the documentation of the legacy standalone Gateway Server. This server is deprecated and will be removed at some point. You should use the Caddy module instead.
|the URL of the API|
|the path to an OpenAPI v3 file containing Link definitions|
|the maximum number of resources to push (|
|instructs the gateway server to send Preload hints in 103 Early Hints response. Enabling this setting is usually useless because the gateway server doesn't supports JSON streaming yet, consequently the server will have to wait for the full JSON response to be received from upstream before being able to compute the Link headers to send. When the full response is available, we can send the final response directly. Better send Early Hints responses as soon as possible, directly from the upstream application. The proxy will forward them even if this option is not enabled.|
|the directory where to store Let's Encrypt certificates|
|a comma separated list of hosts for which Let's Encrypt certificates must be issued|
|the address to listen on (example: |
|a cert file (to use a custom certificate)|
|a key file (to use a custom certificate)|
|set to |
|set to |
|maximum duration for reading the entire request, including the body, set to |
|must contain the secret key to valid subscribers' JWT, can be omitted if |
|maximum duration before timing out writes of the response, set to |
ACME_HOSTS or both
KEY_FILE are provided, an HTTPS server supporting HTTP/2 connection will be started.
If not, an HTTP server will be started (not compatible with HTTP/2 Server Push, and not secure).