AAP-63668 Fix security hot spot by deleting it #16258
Open
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.




Trigger sonar cube runs. I've deleted the "security hotspot". I want to see if sonarcube recognizes the issue as fixed and how it informs me of that in it's UI.
SUMMARY
ISSUE TYPE
COMPONENT NAME
ADDITIONAL INFORMATION
Note
Low Risk
Small, non-functional change limited to logging in webhook notifications; main risk is reduced visibility into unexpected redirect behavior during troubleshooting.
Overview
Removes the
logger.warning(...)emitted when webhook delivery receives a301/307redirect; the backend still retries by following theLocationheader up toMAX_RETRIES.This reduces logging/observability around redirects without changing delivery behavior.
Written by Cursor Bugbot for commit d292e24. This will update automatically on new commits. Configure here.