Why can't the Any Paths rule be merged with other rules?
Short answer
Because Any Paths is not a path pattern but the mandatory base rule of the host group. Merge gathers rules that have a path under a single path; Any paths has no path, it already covers all the paths that do not have their own rule, and it completes the Check Fields sections that the other rules do not define. There is exactly one Any paths in every host group: every time the group rules are written, Any paths is set up again with its default if it is missing, so it cannot be folded into a glob rule and eliminated. While Any paths is in the selection, the Merge button stays disabled; the operation is also rejected on the server side. To change Any paths, Edit is used, and to return it to the default, Delete is used.
How Does It Work?
| Operation | In Any paths |
|---|---|
| Edit (fields other than the path: Allowed methods, Path length, Path depth, OWASP) | Available; the path field is locked as Any Paths (What is the Any Paths rule?) |
| Adding and editing Check fields | Available; the common inspections can be edited but cannot be deleted |
| Delete | Resetting, not deleting (Can I delete the Any Paths rule?) |
| Merge | Not available; the button is disabled while Any paths is in the selection |
| Changing the path | Not available |
- Merge requires at least two rules, and Any paths must not be in the selection (WAF Rules · Merge).
- Merging the other rules: How do I merge several page types into one rule (Merge)?
- The inspection of unknown paths is configured through Any paths: How is a request that matches no page type inspected?
Common Misconceptions
- "Any paths can be replaced with a glob rule." Any paths is mandatorily present in every group and cannot be removed; the settings of unknown paths are kept in Any paths itself.
- "If Merge is disabled, there is a problem in the selection." If Any paths is in the selection or fewer than two rules are selected, the button is always disabled.
How it is done in the documentation
