-
Notifications
You must be signed in to change notification settings - Fork 158
[Bug]: Linkchecker reveals bad links #2002
Copy link
Copy link
Open
Labels
bugSomething isn't workingSomething isn't workinggood first issueGood for newcomersGood for newcomersproduct/wafIssues related to F5 WAF for NGINXIssues related to F5 WAF for NGINXtriageThis issue has been flagged for review during weekly triageThis issue has been flagged for review during weekly triage
Description
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't workinggood first issueGood for newcomersGood for newcomersproduct/wafIssues related to F5 WAF for NGINXIssues related to F5 WAF for NGINXtriageThis issue has been flagged for review during weekly triageThis issue has been flagged for review during weekly triage
Type
Fields
Give feedbackNo fields configured for issues without a type.
Describe the problem you have identified
Our internal linkchecker has revealed a couple of bad links in https://docs.nginx.com/waf/policies/parameter-reference/
Per RFC 2606, we should use
example.comfor all such links (mywebsite.com is actually listed as a badware risk in our filters.Which product or products does this problem relate to?
F5 WAF for NGINX
If necessary, explain any additional steps to reproduce the problem.
No response
What is the expected or desired behaviour?
No response
Is this problem specific to a particular platform or software version?
No response
Any additional information
No response