HTTP_RULE_RES_YIELD was used where HTTP_RULE_RES_FYIELD should be used.
Hopefully, aside from debug traces, both return values were treated
equally. Let's fix that to prevent confusion and from causing bugs
in the future.
It may be backported in 3.2 with
0846638 ("MEDIUM: stream: interrupt
costly rulesets after too many evaluations") if it easily applies
if (s->rules_bcount++ >= global.tune.max_rules_at_once && !(act_opts & ACT_OPT_FINAL)) {
s->current_rule = rule;
s->flags |= SF_RULE_FYIELD;
- rule_ret = HTTP_RULE_RES_YIELD;
+ rule_ret = HTTP_RULE_RES_FYIELD;
task_wakeup(s->task, TASK_WOKEN_MSG);
goto end;
}