Misprint: 'mause' instead of 'pause'

[john9x]

haproxy/src/http_act.c

Line 2131 in 3eebd5f

memprintf(err, "unexpected character '%c' in rule 'mause'", *res);

[wtarreau]

Oh indeed, than you! Quick question, since you made the effort of opening an issue for this, are you interested in proposing a patch for it ? If so, please have a look at the CONTRIBUTING file for what format is expected for patches etc and feel free to send it. I can even point you to a few more locations that require comparable fixes in dev8 if you're interested!

[john9x]

I'm sorry but I'm not a C developer at all. I just try to do something like

http-request pause %[var(txn.rate_limit_pause)] if { var(txn.rate_limit_pause) -m int gt 0 }

and when I see error detected in backend 'api' while parsing 'http-request pause' rule : unexpected character '%' in rule 'mause' I decided to check the source code :)

BTW, how to achieve dynamic pause from var?
example below not working

http-request pause %[var(txn.rate_limit_pause)] if { var(txn.rate_limit_pause) -m int gt 0 }
or
http-request pause var(txn.rate_limit_pause) if { var(txn.rate_limit_pause) -m int gt 0 }

[wtarreau]

I'm sorry but I'm not a C developer at all.

No problem at all, you don't even have to be sorry. I was asking in case you were interested an too shy to propose :-)

I'm seeing this in the doc:

pause { <timeout> | <expr> }

So unless there is a bug, it should accept your second syntax. What version are you running on ?

[john9x]

What version are you running on ?

haproxy version is 3.2.15-04ef5bd69

[john9x]

second syntax gives

[ALERT]    (690677) : config : parsing [/etc/haproxy/config/haproxy.cfg:291] : error detected in backend 'api' while parsing 'http-request pause' rule : unexpected character 'v' in rule 'mause'.

[wtarreau]

For me in 3.2 the config loads and works! I even tried with your exact version and I copy-pasted your config line! And since there hasn't ever been a version with only integer and no expr, it cannot be a problem of version. It's puzzling.

Can you please share the output of "haproxy -vv" ? I'm wondering if it could be a parsing subtlety depending on the libc in use or something like this.

[john9x]

k8s pod, base image haproxytech/haproxy-ubuntu:3.2

root@haproxy-web-5746f45f54-ltmcx:/# haproxy -vv
HAProxy version 3.2.15-04ef5bd69 2026/03/19 - https://haproxy.org/
Status: long-term supported branch - will stop receiving fixes around Q2 2030.
Known bugs: http://www.haproxy.org/bugs/bugs-3.2.15.html
Running on: Linux 6.12.68-92.122.amzn2023.aarch64 #1 SMP Mon Feb  9 10:42:33 UTC 2026 aarch64
Build options :
  TARGET  = linux-glibc
  CC      = cc
  CFLAGS  = -O2 -g -fwrapv -fvect-cost-model=very-cheap
  OPTIONS = USE_PTHREAD_EMULATION=1 USE_LINUX_TPROXY=1 USE_GETADDRINFO=1 USE_OPENSSL_AWSLC=1 USE_LUA=1 USE_SLZ=1 USE_TFO=1 USE_QUIC=1 USE_PROMEX=1 USE_PCRE2=1 USE_PCRE2_JIT=1
  DEBUG   =

Feature list : -51DEGREES +ACCEPT4 +BACKTRACE -CLOSEFROM +CPU_AFFINITY +CRYPT_H -DEVICEATLAS +DL -ENGINE +EPOLL -EVPORTS +GETADDRINFO -KQUEUE -LIBATOMIC +LIBCRYPT +LINUX_CAP +LINUX_SPLICE +LINUX_TPROXY +LUA +MATH -MEMORY_PROFILING +NETFILTER +NS -OBSOLE
TE_LINKER +OPENSSL +OPENSSL_AWSLC -OPENSSL_WOLFSSL -OT -PCRE +PCRE2 +PCRE2_JIT -PCRE_JIT +POLL +PRCTL -PROCCTL +PROMEX +PTHREAD_EMULATION +QUIC -QUIC_OPENSSL_COMPAT +RT +SLZ +SSL -STATIC_PCRE -STATIC_PCRE2 +TFO +THREAD +THREAD_DUMP +TPROXY -WURFL -ZLIB
+ACME

Default settings :
  bufsize = 16384, maxrewrite = 1024, maxpollevents = 200

Built with multi-threading support (MAX_TGROUPS=32, MAX_THREADS=1024, default=8).
Built with SSL library version : OpenSSL 1.1.1 (compatible; AWS-LC 1.69.0)
Running on SSL library version : AWS-LC 1.69.0
SSL library supports TLS extensions : yes
SSL library supports SNI : yes
SSL library FIPS mode : no
SSL library supports : TLSv1.0 TLSv1.1 TLSv1.2 TLSv1.3
QUIC: connection socket-owner mode support : yes
QUIC: GSO emission support : yes
Built with Lua version : Lua 5.4.6
Built with the Prometheus exporter as a service
Built with network namespace support.
Built with libslz for stateless compression.
Compression algorithms supported : identity("identity"), deflate("deflate"), raw-deflate("deflate"), gzip("gzip")
Built with transparent proxy support using: IP_TRANSPARENT IPV6_TRANSPARENT IP_FREEBIND
Built with PCRE2 version : 10.42 2022-12-11
PCRE2 library supports JIT : yes
Encrypted password support via crypt(3): yes
Built with gcc compiler version 13.3.0

Available polling systems :
      epoll : pref=300,  test result OK
       poll : pref=200,  test result OK
     select : pref=150,  test result OK
Total: 3 (3 usable), will use epoll.

Available multiplexer protocols :
(protocols marked as <default> cannot be specified using 'proto' keyword)
       quic : mode=HTTP  side=FE     mux=QUIC  flags=HTX|NO_UPG|FRAMED
         h2 : mode=HTTP  side=FE|BE  mux=H2    flags=HTX|HOL_RISK|NO_UPG
  <default> : mode=HTTP  side=FE|BE  mux=H1    flags=HTX
         h1 : mode=HTTP  side=FE|BE  mux=H1    flags=HTX|NO_UPG
       fcgi : mode=HTTP  side=BE     mux=FCGI  flags=HTX|HOL_RISK|NO_UPG
  <default> : mode=SPOP  side=BE     mux=SPOP  flags=HOL_RISK|NO_UPG
       spop : mode=SPOP  side=BE     mux=SPOP  flags=HOL_RISK|NO_UPG
  <default> : mode=TCP   side=FE|BE  mux=PASS  flags=
       none : mode=TCP   side=FE|BE  mux=PASS  flags=NO_UPG

Available services : prometheus-exporter
Available filters :
        [BWLIM] bwlim-in
        [BWLIM] bwlim-out
        [CACHE] cache
        [COMP] compression
        [FCGI] fcgi-app
        [SPOE] spoe
        [TRACE] trace

[wtarreau]

It looks completely standard. I would like to make a simple test to validate if it's related to the var() sample fetch or the use of the expression. Could you please try with this ?

http-request pause int(1000)

It must parse correctly and cause a pause of one second (and for me it works here with your exact commit number).

[john9x]

Mystical! I rolled back the changes, checked the config using haproxy -c, tried different options, reapplied the problematic ones, and now haproxy -c doesn't show any errors.

[wtarreau]

Maybe you had a bad character left in the config itself that was not on the part you copy-pasted here!