|
|
|
@ -752,7 +752,7 @@ Consul will not enable TLS for the HTTP API unless the `https` port has been ass
|
|
|
|
|
to the Consul raft log in environments where health checks have volatile output like |
|
|
|
|
timestamps, process ids, ... |
|
|
|
|
|
|
|
|
|
* <a name="discovery_max_stale"></a><a href="#discovery_max_stale">`discovery_max_stale`</a> - Enables |
|
|
|
|
* <a name="discovery_max_stale"></a><a href="#discovery_max_stale">`discovery_max_stale`</a> - Enables |
|
|
|
|
stale requests for all service discovery HTTP endpoints. This is equivalent to the |
|
|
|
|
[`max_stale`](#max_stale) configuration for DNS requests. If this value is zero (default), all service |
|
|
|
|
discovery HTTP endpoints are forwarded to the leader. If this value is greater than zero, any Consul server |
|
|
|
@ -1360,4 +1360,4 @@ items which are reloaded include:
|
|
|
|
|
* <a href="#node_meta">Node Metadata</a> |
|
|
|
|
* <a href="#telemetry-prefix_filter">Metric Prefix Filter</a> |
|
|
|
|
* <a href="#discard_check_output">Discard Check Output</a> |
|
|
|
|
* <a href="#limits">RPC rate limiting</a> |
|
|
|
|
* <a href="#limits">RPC rate limiting</a> |
|
|
|
|