From bbd8492c2220f1b4a11ee0d7319da9578f2c0845 Mon Sep 17 00:00:00 2001 From: Willy Tarreau Date: Mon, 23 Feb 2026 15:42:04 +0100 Subject: [PATCH] CLENAUP: cfgparse: accept-invalid-http-* does not support "no"/"defaults" Some options do not support "no" nor "defaults" and they're placed after the check for their absence. However, "accept-invalid-http-request" and "accept-invalid-http-response" still used to check for the flags that come with these prefixes, but Coverity noticed this was dead code in github issue #3272. Let's just drop the test. No backport needed as it's just dead code. --- src/cfgparse-listen.c | 13 +------------ 1 file changed, 1 insertion(+), 12 deletions(-) diff --git a/src/cfgparse-listen.c b/src/cfgparse-listen.c index 3bce9dd0b..12d42782e 100644 --- a/src/cfgparse-listen.c +++ b/src/cfgparse-listen.c @@ -2454,18 +2454,7 @@ stats_error_parsing: } curproxy->no_options2 &= ~val; - curproxy->options2 &= ~val; - - switch (kwm) { - case KWM_STD: - curproxy->options2 |= val; - break; - case KWM_NO: - curproxy->no_options2 |= val; - break; - case KWM_DEF: /* already cleared */ - break; - } + curproxy->options2 |= val; err_code |= ERR_WARN; goto out; -- 2.47.3