Add security response id to AppSec redirect response#5060
Merged
Conversation
9004838 to
a813094
Compare
Strech
approved these changes
Nov 19, 2025
BenchmarksBenchmark execution time: 2025-11-19 10:17:06 Comparing candidate commit a813094 in PR branch Found 1 performance improvements and 0 performance regressions! Performance is the same for 43 metrics, 2 unstable metrics. scenario:profiling - intern_all 1000 repeated strings
|
6 tasks
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.
What does this PR do?
This PR adds substitution of
[security_response_id]placeholder for AppSec redirect responseLocationheader.Motivation:
According to RFC,
[security_response_id]needs to be also substituted in theLocationheader, when the client has AppSec configured to redirect on a detected attack.Change log entry
No. There will be one change log entry for the security response id, which was already added in #5049.
Additional Notes:
APPSEC-59951.
How to test the change?
CI and manual testing.