Add option to sanitize sensitive headers #60
Merged
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.
This PR adds the possibility to sanitize some headers that shouldn't be stored in logs, especially if you are using some third-party logging driver. For example, most likely we don't want to send jwt tokens from the Authorization header, or some IP addresses, etc. Because of that, I added one more configuration field to define headers that should be sanitized before sending.
I didn't want to add some headers in the configuration by default, because maybe it would be backward incompatible since it would be a change of existing behavior.
Let me know if you have any questions or suggestions. 😊