Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

update custom headers to mention 1.9 is required #13155

Merged
merged 2 commits into from
Dec 1, 2021
Merged

update custom headers to mention 1.9 is required #13155

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
38b7e67
update custom headers to mention 1.9 is required
rowansmithhc Nov 16, 2021
1648e4d
Update website/content/docs/configuration/listener/tcp.mdx
rowansmithhc Nov 23, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions website/content/docs/configuration/listener/tcp.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -22,7 +22,7 @@ specify [`api_addr`][api-addr] and [`cluster_addr`][cluster-addr] so Vault will
advertise the correct address to other nodes.

## Listener's custom response headers
Vault supports defining custom HTTP response headers for the root path (`/`) and also on API endpoints (`/v1/*`).
As of version 1.9, Vault supports defining custom HTTP response headers for the root path (`/`) and also on API endpoints (`/v1/*`).
The headers are defined based on the returned status code. For example, a user can define a list of
custom response headers for the `200` status code, and another list of custom response headers for
the `307` status code. There is a `"/sys/config/ui"` [API endpoint](/api/system/config-ui) which allows users
Expand Down Expand Up @@ -260,8 +260,8 @@ listener "tcp" {

### Configuring custom http response headers

This example shows configuring custom http response headers. Operators can configure
`"custom_response_headers"` sub-stanza in the listener stanza to set custom http
Note: Requires Vault version 1.9 or newer. This example shows configuring custom http response headers.
Operators can configure `"custom_response_headers"` sub-stanza in the listener stanza to set custom http
headers appropriate to their applications. Examples of such headers are `"Strict-Transport-Security"`
and `"Content-Security-Policy"` which are known HTTP headers, and could be configured to harden
the security of an application communicating with the Vault endpoints. Note that vulnerability
Expand Down