Update options.html.md

This commit is contained in:
James Phillips 2017-06-24 15:28:23 -07:00 committed by GitHub
parent 2742efbd64
commit 6e1ee02689
1 changed files with 6 additions and 7 deletions

View File

@ -749,7 +749,7 @@ Consul will not enable TLS for the HTTP API unless the `https` port has been ass
}
```
This has been deprecated in Consul 0.9.0. Setting this value will set `http_config.response_headers`
This has been deprecated in Consul 0.8.5. Setting this value will set `http_config.response_headers`
instead for backwards compatibility.
* <a name="http_config"></a><a href="#http_config">`http_config`</a>
@ -757,12 +757,11 @@ Consul will not enable TLS for the HTTP API unless the `https` port has been ass
<br><br>
The following sub-keys are available:
* <a name="allow_stale"></a><a href="#allow_stale">`allow_stale`</a> - Enables a stale query
for DNS information. This allows any Consul server, rather than only the leader, to service
the request. The advantage of this is you get linear read scalability with Consul servers.
In versions of Consul prior to 0.7, this defaulted to false, meaning all requests are serviced
by the leader, providing stronger consistency but less throughput and higher latency. In Consul
0.7 and later, this defaults to true for better utilization of available servers.
* <a name="allow_stale"></a><a href="#allow_stale">`allow_stale`</a> - Enables a stale query
by default for HTTP queries. This allows any Consul server, rather than only the leader, to service
the request. The advantage of this is you get linear read scalability with Consul servers.
This defaults to false. Use this with extreme caution as this will apply to *all* read queries such
as for the catalog and the key/value store, so clients will see potentially inconsistent results.
* <a name="response_headers"></a><a href="#response_headers">`response_headers`</a>
This object allows adding headers to the HTTP API responses.