mirror of
https://github.com/owasp-modsecurity/ModSecurity.git
synced 2026-01-13 06:17:05 +03:00
Allow all phase 5 rules to run. See %425.
This commit is contained in:
3
CHANGES
3
CHANGES
@@ -1,6 +1,9 @@
|
|||||||
14 Dec 2007 - 2.1.5-rc1
|
14 Dec 2007 - 2.1.5-rc1
|
||||||
-----------------------
|
-----------------------
|
||||||
|
|
||||||
|
* Fixed issue where only the first phase 5 rule would run when the
|
||||||
|
request was intercepted in an earlier phase.
|
||||||
|
|
||||||
* Stricter configuration parsing. Disruptive actions, meta actions and
|
* Stricter configuration parsing. Disruptive actions, meta actions and
|
||||||
phases are no longer allowed in a chained rule.
|
phases are no longer allowed in a chained rule.
|
||||||
|
|
||||||
|
|||||||
@@ -731,7 +731,7 @@ apr_status_t msre_ruleset_process_phase(msre_ruleset *ruleset, modsec_rec *msr)
|
|||||||
}
|
}
|
||||||
else
|
else
|
||||||
if (rc == RULE_MATCH) {
|
if (rc == RULE_MATCH) {
|
||||||
if (msr->was_intercepted) {
|
if ((msr->phase == msr->intercept_phase) && msr->was_intercepted) {
|
||||||
/* If the transaction was intercepted we will
|
/* If the transaction was intercepted we will
|
||||||
* go back. Do note that we are relying on the
|
* go back. Do note that we are relying on the
|
||||||
* rule to know if it is a part of a chain and
|
* rule to know if it is a part of a chain and
|
||||||
|
|||||||
Reference in New Issue
Block a user