From bed69cefb21af4eb95026306fcc952a114b5a2a9 Mon Sep 17 00:00:00 2001 From: preetapan Date: Sat, 21 Oct 2017 20:59:47 -0500 Subject: [PATCH] Update watches.html.md --- website/source/docs/agent/watches.html.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/website/source/docs/agent/watches.html.md b/website/source/docs/agent/watches.html.md index d00ab850a2..d7e098c897 100644 --- a/website/source/docs/agent/watches.html.md +++ b/website/source/docs/agent/watches.html.md @@ -66,11 +66,12 @@ the `args` to run under a shell, eg. `"args": ["sh", "-c", "..."]`. ### HTTP endpoint A HTTP handler sends a HTTP request when a watch is invoked. The JSON -invocation info is sent as a payload along the request. The response contains the Consul index as a header named `X-Consul-Index`. +invocation info is sent as a payload along the request. +The response also contains the Consul index as a header named `X-Consul-Index`. The HTTP handler can be configured by setting `handler_type` to `http`. Additional handler options are set using `http_handler_config`. The only required parameter is the `path` field which specifies the URL to the HTTP -endpoint. Consul uses `POST` as the default http method, but this can be set to any method. +endpoint. Consul uses `POST` as the default HTTP method, but this is also configurable. Other optional fields are `header`, `timeout` and`tls_skip_verify`. The watch invocation data is always sent as a JSON payload. Here is an example configuration: