F5 WAF for NGINX 5.10 release #1504
Merged
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
doc: Update policy schema Compiler 11.585.0-wafmc-000-update-doc-path-16124977 (02ed8c3c)
Update the table to correct names
more oss typos
This commit adds the "User-defined browser control" feature page to the policy section of F5 WAF for NGINX documentation, and changelog entries for 2024 and 2023 before the v4/v5 split. It also adds a notice to the top of the deny/allow IP feature page and supported feature table directing users to use the IP addresses feature instead, which is newer and deprecates the latter. --------- Co-authored-by: Jon Torre <78599298+JTorreG@users.noreply.github.com>
github-actions
bot
added
documentation
✅ Deploy Preview will be available once build job completes!
|
Corrected the spelling of 'cumulative' in the policy description.
…o waf-release-5.10
ohad-perets
approved these changes
Dec 1, 2025
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
Full PR description TBD.
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. ↩