Inject Custom Response Headers By Status #2587
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
There was a problem hiding this comment.
Thanks for the extensive docs, I'm tagging @Dan-Heath for a look at this as well
Dan-Heath
reviewed
Nov 17, 2022
kheina
force-pushed
the
daniellemiu_add-custom-response-headers
branch
from
d880fb1
to
a313dd1
Compare
tmessi
reviewed
Nov 29, 2022
tmessi
approved these changes
Nov 29, 2022
tmessi
reviewed
Nov 30, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
relies on go-secure-stdlib#49 and go-secure-stdlib#51
Preview documentation page
tested using boundary-local-env and performing a login via the frontend