Content Cache Backends Config

Learn about configurations >

• backend-hostname | string

  The hostname to use as the SNI and HTTP Host header when proxying to HTTPS backends. Required when backends use https://. Must be a valid DNS hostname (max 255 characters, alphanumeric segments separated by dots). Example: backend-hostname=backend.example.com

• backends | string

  A comma-separated list of backend URLs in the form http://ip:port or https://ip:port. If multiple URLs are provided, the access to the backends will be load-balanced.

• fail-timeout | string

  Default: 30s

  The time to wait before using a backend after failure. The other backend will be used instead. No effect if only one backend is specified. The value should a positive int followed by s for seconds, m for minutes, or h for hours.

• healthcheck-interval | int

  Default: 10000

  The time between two health checks (in milliseconds)

• healthcheck-path | string

  Default: /

  The path part of the URL to query the healthcheck endpoint.

• healthcheck-ssl-verify | boolean

  Default: True

  A boolean to bypass ssl verification for healthchecks.

• healthcheck-valid-status | string

  Default: 200

  A comma-separated list of HTTP response code(s) which are considered as valid during health checks.

• proxy-cache-valid | string

  Default: []

  A list of HTTP response code(s) followed by a cache valid duration. For example ["200 302 1h "", "404 1m"], which would mean 200 and 302 responses are cached for 1 hour and 404 responses are cached for 1 minute. This configuration is passed to nginx proxy-cache-valid (https://nginx.org/en/docs/http/ngx_http_proxy_module.html#proxy_cache_valid).