upstream/vault
1
0
Fork 0
mirror of https://github.com/hashicorp/vault.git synced 2026-06-11 01:42:06 -04:00
Code Issues Projects Releases Packages Wiki Activity Actions 11

Fixed typo for 'forward' value in relation to caching (#12199)

Browse source
This commit is contained in:
Rowan Smith 2021-07-29 21:41:08 +10:00 committed by GitHub
parent 62c0cdb216
commit b558cb589d
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
2 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
website/content/docs/agent/caching/index.mdx
View file

@ -209,7 +209,7 @@ page.
or `"never"`.
- `when_inconsistent` `(string: optional)` - Set to one of `"fail"`, `"retry"`,
or `"forward-active_node"`.
or `"forward"`.
### Configuration (Persist)

2
website/content/docs/enterprise/consistency.mdx
View file

@ -192,7 +192,7 @@ The option `when_inconsistent` controls how stale reads are prevented:
- `"fail"` means that when a `412` response is seen, it is returned to the client
- `"retry"` means that `412` responses will be retried automatically by Agent,
so the client doesn't have to deal with them
- `"forward-active-node"` makes Agent provide the
- `"forward"` makes Agent provide the
`X-Vault-Inconsistent: forward-active-node` header as described above under
Conditional Forwarding