owasp-modsecurity / owasp-modsecurity/ModSecurity
Sub-phases
Open
@zimmerle is already working on this.
Since Oct 17, 2013.
RIP - Type - Feature
- Dominant language
- C++
- Stars
- 9.8k
- Forks
- 1.8k
- Avg merge
- 2h 46m
- Merged PRs (30d)
- 1
Description
MODSEC-217: It would be very useful to have sub-phases on top of existing phases to sort directive processing order.
Ex:
- I have a lot of generic phase:2 rules (CRS or other)
- One of the generic phase:2 rule needs to run after all other phase:2 rules
- I have to insert my custom rules in the middle of the processing to influence the last generic rule
- It's annoying to insert my specific rules in the middle of the others, because mostof other directives (rewriting, etc.) will usually be defined elsewhere (maybe in macros)
- If I need to specify them inside a location, it does not work
It would be very useful to specify some rules as, for instance, phase:2.9 to force them after the ones defined as phase:2, phase:2.3, etc.
This would also allow to update a rule previously defined in phase:2.5 with "phase:2.1,ctl:ruleUpdateTargetById:..."
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.