-
Notifications
You must be signed in to change notification settings - Fork 56
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
Redact HTTP query values from logs #930
Merged
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
austinvazquez
force-pushed
the
redact-http-query-values
branch
3 times, most recently
from
November 9, 2023 23:09
2d7b5ef
to
ee77932
Compare
turan18
previously approved these changes
Nov 10, 2023
Kern--
requested changes
Nov 10, 2023
austinvazquez
force-pushed
the
redact-http-query-values
branch
2 times, most recently
from
November 13, 2023 16:53
3874c72
to
a749a09
Compare
Kern--
requested changes
Nov 13, 2023
austinvazquez
force-pushed
the
redact-http-query-values
branch
6 times, most recently
from
November 14, 2023 19:40
d9b4cae
to
919f5e0
Compare
turan18
reviewed
Nov 14, 2023
austinvazquez
force-pushed
the
redact-http-query-values
branch
from
November 15, 2023 17:58
919f5e0
to
6130136
Compare
HTTP client logs are mostly disabled with the exception of a request retry log. The issue observed is that error messages may contain the full HTTP request including the query component which can contain sensitive information like credentials or session tokens. To prevent leaking sensitive information, this change will redact HTTP query values from log messages. Signed-off-by: Austin Vazquez <[email protected]>
austinvazquez
force-pushed
the
redact-http-query-values
branch
from
November 15, 2023 18:00
6130136
to
9261f46
Compare
Kern--
approved these changes
Nov 17, 2023
turan18
approved these changes
Nov 17, 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.
Issue #, if available:
N/A
Description of changes:
HTTP client logs are mostly disabled with the exception of a request retry log. The issue observed is that error messages may contain the full HTTP request including the query component which can contain sensitive information like credentials or session tokens. To prevent leaking sensitive information, this change will redact HTTP query values from log messages.
Testing performed:
Added unit tests and benchmarks to measure overhead for redacting HTTP query values from errors in logs.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.