From 15c0a72f742b0536af66e467536c2e66d80dca29 Mon Sep 17 00:00:00 2001 From: James Phillips Date: Fri, 1 Sep 2017 22:25:28 -0700 Subject: [PATCH] Update options.html.md --- website/source/docs/agent/options.html.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/source/docs/agent/options.html.md b/website/source/docs/agent/options.html.md index 7dcad73d7d..ff92b6d934 100644 --- a/website/source/docs/agent/options.html.md +++ b/website/source/docs/agent/options.html.md @@ -1252,7 +1252,7 @@ Consul will not enable TLS for the HTTP API unless the `https` port has been ass Starting in Consul 0.7 and later, node addresses in responses to HTTP requests will also prefer a node's configured WAN address when querying for a node in a remote - datacenter. An [`X-Consul-Translate-Addresses`](/api/index.html#translate_header) header + datacenter. An [`X-Consul-Translate-Addresses`](/api/index.html#translated-addresses) header will be present on all responses when translation is enabled to help clients know that the addresses may be translated. The `TaggedAddresses` field in responses also have a `lan` address for clients that need knowledge of that address, regardless of translation.