Skip to content

Add allowed_response_headers #6115

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.

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

Merged
merged 15 commits into from
Feb 5, 2019
Merged

Add allowed_response_headers #6115

merged 15 commits into from
Feb 5, 2019

Conversation

jefferai
Copy link
Member

@jefferai jefferai commented Jan 27, 2019

Similar to passthrough_request_headers but going the other way.

Fixes #5031

@jefferai jefferai added this to the 1.0.3 milestone Jan 27, 2019
@jefferai jefferai added the ui label Jan 27, 2019
@jefferai jefferai force-pushed the allowed-response-headers branch from e5d6531 to 4f8e52d Compare January 29, 2019 16:58
kalafut
kalafut previously approved these changes Feb 1, 2019
@jefferai jefferai merged commit 20423f7 into master Feb 5, 2019
@jefferai jefferai deleted the allowed-response-headers branch February 5, 2019 21:02
jefferai added a commit that referenced this pull request Feb 8, 2019
Although removing the authentication header is good defense in depth,
for forwarding mechanisms that use the raw request, we never add it
back. This caused perf standby tests to throw errors. Instead, once
we're past the point at which we would do any raw forwarding, but before
routing the request, remove the header.

To speed this up, a flag is set in the logical.Request to indicate where
the token is sourced from. That way we don't iterate through maps
unnecessarily.
jefferai added a commit that referenced this pull request Feb 11, 2019
* Fixes a regression in forwarding from #6115

Although removing the authentication header is good defense in depth,
for forwarding mechanisms that use the raw request, we never add it
back. This caused perf standby tests to throw errors. Instead, once
we're past the point at which we would do any raw forwarding, but before
routing the request, remove the header.

To speed this up, a flag is set in the logical.Request to indicate where
the token is sourced from. That way we don't iterate through maps
unnecessarily.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants