create release branch 5.11 #1612
Draft
+38
−1
Conversation
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
github-actions
bot
added
documentation
✅ Deploy Preview will be available once build job completes!
|
doc: Update policy schema Compiler 11.596.0-nap-release-5-11-0-16303952 (b179e9dd)
ADubhlaoich
reviewed
Dec 22, 2025
Member
ADubhlaoich
left a comment
ADubhlaoich
left a comment
There was a problem hiding this comment.
Adding an initial correction: I'll stay aware for further changes.
mjang
reviewed
Dec 29, 2025
| <td>Yes</td> | ||
| <td>array of objects</td> | ||
| <td>Defines behavior when signatures found within a signature-set are detected in a request. Settings are cumulative, so if a signature is found in any set with block enabled, that signature will have block enabled.</td> | ||
| <td>Defines behavior when signatures found within a signature-set are detected in a request. Settings are culmulative, so if a signature is found in any set with block enabled, that signature will have block enabled.</td> |
Contributor
There was a problem hiding this comment.
The proposed change is a typo
Suggested change
| <td>Defines behavior when signatures found within a signature-set are detected in a request. Settings are culmulative, so if a signature is found in any set with block enabled, that signature will have block enabled.</td> | |
| <td>Defines behavior when signatures found within a signature-set are detected in a request. Settings are cumulative, so if a signature is found in any set with block enabled, that signature will have block enabled.</td> |
| ### Resolved issues | ||
|
|
||
| - 13470 - An invalid cookie in the Cookie header causes all subsequent cookies to be ignored, resulting in incomplete parsing and missing logs downstream | ||
| - 13340 - Nginx WAF leaked sockets and terminated on-going requests during graceful reload of NGINX (SIGHUP) |
Contributor
There was a problem hiding this comment.
Suggested change
| - 13340 - Nginx WAF leaked sockets and terminated on-going requests during graceful reload of NGINX (SIGHUP) | |
| - 13340 - F5 WAF for NGINX leaked sockets and terminated on-going requests during graceful reload of NGINX (SIGHUP) |
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.
Proposed changes
Checklist
Before sharing this pull request, I completed the following checklist:
Footnotes
Potentially sensitive information includes personally identify information (PII), authentication credentials, and live URLs. Refer to the style guide for guidance about placeholder content. ↩