feat: forward x-request-id headers #270
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
johnnagro
force-pushed
the
johnnagro/x-request-id-forwarding/0
branch
from
d73cabb to
8cb1510
Compare
macdiesel
approved these changes
May 16, 2023
johnnagro
force-pushed
the
johnnagro/x-request-id-forwarding/0
branch
from
8cb1510 to
18af41d
Compare
This was referenced May 16, 2023
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.
Description
If our OAuth Client is being used in the context of a request with a
X-Request-IDheader present, pass this header along into the OAuth Client request request to aid in traceability.crumis already a requirement viaedx-django-utilsReferences