Content Cache Backends Config
Channel | Revision | Published | Runs on |
---|---|---|---|
latest/edge | 30 | Yesterday | |
latest/edge | 1 | 04 Oct 2024 |
juju deploy content-cache-backends-config --channel edge
Deploy universal operators easily with Juju, the Universal Operator Lifecycle Manager.
Platform:
-
backends | string
A comma-separated list of IPs. If multiple IPs are provided, the access to the backends will be load-balanced.
-
backends-path | string
Default: /
The path part of the URL to query the backends.
-
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.
-
hostname | string
The hostname for the virtual host for this set of backends.
-
path | string
Default: /
The location to serve with this set of backends. Does not support regex.
-
protocol | string
Default: https
The protocol to request the backends. Can be http or https.
-
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).