docs: document SECURITY_WAF_VIOLATION_TRANSPARENT for $app_protect_outcome_reason#2095
Open
zahava-brown wants to merge 1 commit into
Open
docs: document SECURITY_WAF_VIOLATION_TRANSPARENT for $app_protect_outcome_reason#2095zahava-brown wants to merge 1 commit into
zahava-brown wants to merge 1 commit into
Conversation
…tcome_reason WAFMC-14828: the nginx access-log variable $app_protect_outcome_reason can emit SECURITY_WAF_VIOLATION_TRANSPARENT for requests allowed in transparent (would-block) mode. This brings the access-log documentation to parity with the security-log documentation (content/waf/logging/security-logs.md), which already lists this value.
github-actions
Bot
added
documentation
ohad-perets
reviewed
Jul 5, 2026
JTorreG
approved these changes
Jul 6, 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
3 participants
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.
Proposed changes
The F5 WAF for NGINX access-log variable
$app_protect_outcome_reasoncan emitSECURITY_WAF_VIOLATION_TRANSPARENTfor a request that is allowed while the policyis in transparent (would-block) mode but that would be blocked if the policy were
in blocking mode.
This value is already documented for the security log in
content/waf/logging/security-logs.md, but it was missing from the$app_protect_outcome_reasonvariable reference incontent/waf/logging/access-logs.md. This change adds it, bringing the access-logdocumentation to parity with the security-log documentation.
Type of change
Ref: WAFMC-14828