mirrors/vault
1
0
Fork 0
mirror of https://github.com/hashicorp/vault.git synced 2025-09-10 16:31:07 +02:00
Code Issues Projects Releases Wiki Activity

Merge pull request #2017 from hashicorp/client-redirect-default

Browse Source 
Docs: Update the client redirection defaults
This commit is contained in:
Vishal Nayak 2016-10-19 09:41:50 -04:00 committed by GitHub
commit dbdf068e81
1 changed files with 12 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

24
website/source/docs/concepts/ha.html.markdown
View File

@ -54,11 +54,20 @@ sent over this TLS-protected communication channel, and acted upon by the
active node. The active node then returns a response to the standby, which active node. The active node then returns a response to the standby, which
sends the response back to the requesting client. sends the response back to the requesting client.
## Request Forwarding
If request forwarding is enabled (turned on by default in 0.6.2), clients can
still force the older/fallback redirection behavior (see below) if desired by
setting the `X-Vault-No-Request-Forwarding` header to any non-empty value.
Successful cluster setup requires a few configuration parameters, although some
can be automatically determined.
## Client Redirection ## Client Redirection
This is currently the only mode enabled by default. When a standby node If `X-Vault-No-Request-Forwarding` header in the request is set to a non-empty
receives a request, it will redirect the client using a `307` status code to value, the standby nodes will redirect the client using a `307` status code to
the _active node's_ redirect address. the *active node's* redirect address.
This is also the fallback method used when request forwarding is turned off or This is also the fallback method used when request forwarding is turned off or
there is an error performing the forwarding. As such, a redirect address is there is an error performing the forwarding. As such, a redirect address is
@ -104,15 +113,6 @@ balancer; at that point hopefully the load balancer's configuration will have
been updated to know the address of the current leader. This can cause a been updated to know the address of the current leader. This can cause a
redirect loop and as such is not a recommended setup when it can be avoided. redirect loop and as such is not a recommended setup when it can be avoided.
## Request Forwarding
If request forwarding is enabled (turned on by default in 0.6.2), clients can
still force the older/fallback redirection behavior if desired by setting the
`X-Vault-No-Request-Forwarding` header to any non-empty value.
Successful cluster setup requires a few configuration parameters, although some
can be automatically determined.
### Per-Node Cluster Listener Addresses ### Per-Node Cluster Listener Addresses
Each `listener` block in Vault's configuration file contains an `address` value Each `listener` block in Vault's configuration file contains an `address` value