From e83598b04335ccab9ef381d45c020eb4b3564cf5 Mon Sep 17 00:00:00 2001 From: tummychow Date: Wed, 18 Mar 2015 14:22:36 -0700 Subject: [PATCH] Add doc notes for HTTPS API - the HTTPS API address can be configured just like any other address - the verify_incoming setting also applies to the HTTPS API --- website/source/docs/agent/options.html.markdown | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/website/source/docs/agent/options.html.markdown b/website/source/docs/agent/options.html.markdown index 585d1ffb5..d9729d4ad 100644 --- a/website/source/docs/agent/options.html.markdown +++ b/website/source/docs/agent/options.html.markdown @@ -302,6 +302,7 @@ definitions support being updated during a reload. The following keys are valid: * `dns` - The DNS server. Defaults to `client_addr` * `http` - The HTTP API. Defaults to `client_addr` + * `https` - The HTTPS API. Defaults to `client_addr` * `rpc` - The RPC endpoint. Defaults to `client_addr` * `advertise_addr` Equivalent to @@ -546,7 +547,7 @@ definitions support being updated during a reload. connections make use of TLS and that the client provides a certificate signed by the Certificate Authority from the [`ca_file`](#ca_file). By default, this is false, and Consul will not enforce the use of TLS or verify a client's authenticity. This - only applies to Consul servers since a client never has an incoming connection. + applies to both server RPC and to the HTTPS API. * `verify_outgoing` - If set to true, Consul requires that all outgoing connections