fix: redact sensitive trace headers - #669
Open
rohan-patnaik wants to merge 1 commit into
Open
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
What
Redacts sensitive HTTP headers before writing request and response entries to the trace journal.
The actual request sent to the provider is unchanged. Only the recorded trace output is sanitized.
Why
Trace files are useful for debugging provider calls, but they can currently include headers such as
Authorization, cookies, API keys, tokens, or secrets. That makes trace files risky to share or store.Fixes #617.
Testing
go test ./gollm -run TestJournalingRoundTripperRedactsSensitiveHeaders -count=1git diff --checkNote:
go test ./gollmcurrently fails onTestGetAnthropicModel/explicit_model_is_highest_priorityon the current base branch. That failure is unrelated to this change.