Skip to content

fix: replace mywebsite.com with example.com per RFC 2606#2028

Merged
mjang merged 1 commit into
nginx:mainfrom
AliMahmoudDev:fix/waf-bad-links
Jun 3, 2026
Merged

fix: replace mywebsite.com with example.com per RFC 2606#2028
mjang merged 1 commit into
nginx:mainfrom
AliMahmoudDev:fix/waf-bad-links

Conversation

@AliMahmoudDev
Copy link
Copy Markdown
Contributor

Summary

Replaces mywebsite.com with example.com in the WAF policy parameter reference docs, per RFC 2606 which reserves example.com for documentation and testing purposes.

Changes

  • content/includes/waf/policy.html - Updated the allowRenderingInFramesOnlyFrom field description
  • data/nap-waf/schema/policy.json - Updated the same description in the JSON schema

Testing

  • Verified that mywebsite.com no longer appears anywhere in the affected files
  • Verified that example.com is correctly used as the replacement (consistent with other examples in the same docs)

Fixes #2002

@AliMahmoudDev AliMahmoudDev requested review from a team as code owners June 3, 2026 17:24
@github-actions github-actions Bot added documentation Improvements or additions to documentation product/waf Issues related to F5 WAF for NGINX labels Jun 3, 2026
@AliMahmoudDev
Copy link
Copy Markdown
Contributor Author

I have hereby read the F5 CLA and agree to its terms

Copy link
Copy Markdown
Contributor

@mjang mjang left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you!

@mjang mjang merged commit 09268e9 into nginx:main Jun 3, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation product/waf Issues related to F5 WAF for NGINX

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug]: Linkchecker reveals bad links

2 participants