Repository navigation
appsec: return RET_CODE instead of 200 when APPSEC_FAILURE_ACTION=deny - #167
Merged
Merged
Conversation
With APPSEC_FAILURE_ACTION=deny, an unreachable or failing AppSec applied FALLBACK_REMEDIATION with HTTP 200. Leave the status unset so the ban uses RET_CODE (403 by default). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
sabban
force-pushed
the
fix/appsec-deny-status-captcha-provider-log
branch
from
October 27, 2026 14:45
d4e0008 to
7aa6e4a
Compare
blotus
approved these changes
Oct 28, 2026
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.
With
APPSEC_FAILURE_ACTION=deny, a failed AppSec check served the ban page with HTTP 200; it now usesRET_CODE(403 by default).Adds
t/26_appsec_failure_action_deny.t.🤖 Generated with Claude Code