From c767eebf1f2130447cef3269f4a46ed164410a75 Mon Sep 17 00:00:00 2001 From: Willy Tarreau Date: Fri, 3 Sep 2021 10:23:26 +0200 Subject: [PATCH] BUG/MINOR: vars: do not talk about global section in CLI errors for set-var When attempting to set a variable does not start with the "proc" scope on the CLI, we used to emit "only proc is permitted in the global section" which obviously is a leftover from the initial code. This may be backported to 2.4. --- src/vars.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/vars.c b/src/vars.c index e4e547afd..59f802a30 100644 --- a/src/vars.c +++ b/src/vars.c @@ -1039,7 +1039,7 @@ static int vars_parse_cli_set_var(char **args, char *payload, struct appctx *app goto fail; if (rule.arg.vars.scope != SCOPE_PROC) { - memprintf(&err, "'%s %s': cannot set variable '%s', only scope 'proc' is permitted in the global section.", args[0], args[1], args[2]); + memprintf(&err, "'%s %s': cannot set variable '%s', only scope 'proc' is permitted here.", args[0], args[1], args[2]); goto fail; }