fix: redact cookie headers to prevent information leaks#4897
Merged
Conversation
99e9104 to
fa7db83
Compare
jesmrec
requested changes
Jun 18, 2026
Signed-off-by: Jorge Aguado Recio <jorgeagurec@gmail.com>
Signed-off-by: Jorge Aguado Recio <jorgeagurec@gmail.com>
fa7db83 to
52276e6
Compare
Member
|
QA checks:
|
Member
|
Approved on my side! |
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
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.
Related Issues
Comes from: https://kiteworks.atlassian.net/browse/OC10-95
It depends on the
redact_auth_header_logsconfiguration insetup.xml. If it is set to true, the values of the cookie headers (CookieandSet-Cookie) are replaced with[redacted](the same as theAuthorizationheader)Reference: #4249
ReleaseNotesViewModel.ktcreating a newReleaseNote()with String resources (if required)QA