-
Notifications
You must be signed in to change notification settings - Fork 34
Loggers added #81
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
Merged
Merged
Loggers added #81
Changes from all commits
Commits
Show all changes
24 commits
Select commit
Hold shift + click to select a range
104547d
Reverted Changes
ravishanigarapu 85ca627
removed Unused imports
ravishanigarapu efe5412
Merge branch 'PSMRI:develop' into develop
ravishanigarapu f30feda
Merge branch 'PSMRI:develop' into develop
ravishanigarapu 25d6cbe
Merge branch 'PSMRI:develop' into develop
ravishanigarapu 1e675d9
Merge branch 'PSMRI:develop' into develop
ravishanigarapu 6f93e13
Update application.properties
ravishanigarapu 9ea499d
Merge branch 'PSMRI:develop' into develop
ravishanigarapu fe1908c
Swagger changes
ravishanigarapu 3602722
Merge branch 'PSMRI:develop' into develop
ravishanigarapu e37d6ba
Null Condition Added
ravishanigarapu 2e2d733
Merge branch 'PSMRI:develop' into develop
ravishanigarapu 35237c1
AMM-1456
ravishanigarapu 36dbe68
Indent format
ravishanigarapu 3498d85
User-Agent validation
ravishanigarapu 681977d
wrapper class added
ravishanigarapu f29182e
RestTemplateUtil class created for Headers
ravishanigarapu 44a9c0e
code rabbit issues fixed
ravishanigarapu 4d24d28
if condition added
ravishanigarapu 97659e7
null check
ravishanigarapu 0987627
Merge branch 'develop' into develop
ravishanigarapu 72e5839
loggers Added
ravishanigarapu b6c2e1d
Merge branch 'PSMRI:develop' into develop
ravishanigarapu 3375310
Merge branch 'develop' of https://github.com/ravishanigarapu/TM-API iβ¦
ravishanigarapu File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
π οΈ Refactor suggestion
Avoid logging sensitive headers and use parameterized logging
Concatenating and logging
request.getHeaders()at INFO can expose credentials (e.g., Authorization or cookie tokens) and incurs unnecessary stringβbuilding overhead. Use SLF4J parameterized logs and filter or mask sensitive entries. For example:Implement
filterSensitiveHeaders(...)to redact or remove sensitive keys.π€ Prompt for AI Agents