[Eu postei essa pergunta erroneamente no stackoverflow]
No meu servidor debian buster eu tinha um haproxy funcionando perfeitamente (v1.8), que eu uso para gerenciar certificados para meus sites.
O haproxy escuta a porta 443 e passa as solicitações para um sistema verniz+apache.
Ao atualizar para o debian bullseye, o serviço haproxy (v2.2) não inicia mais, e o log diz:
haproxy[46308]: [ALERT] 048/004148 (46308) : parsing [/etc/haproxy/haproxy.cfg:46] : The 'reqadd' directive is not supported anymore since HAProxy 2.1. Use 'http-r
equest add-header' instead.
As linhas haproxy.cfg responsáveis por este comportamento são
frontend https
# Bind 443 with the generated letsencrypt cert.
bind *:443 ssl crt /etc/letsencrypt/live/qumran2/haproxy.pem
# set x-forward to https
reqadd X-Forwarded-Proto:\ https <-----------|
# set X-SSL in case of ssl_fc <- explained below
http-request set-header X-SSL %[ssl_fc]
# Select a Challenge
acl letsencrypt-acl path_beg /.well-known/acme-challenge/
# Use the challenge backend if the challenge is set
default_backend www-backend
Eu entendo que devo mudar a reqadd X-Forwarded-Proto:\ httpslinha, mas como?
Os documentos dizem:
http-request add-header <name> <fmt> [ { if | unless } <condition> ]
This appends an HTTP header field whose name is specified in <name> and
whose value is defined by <fmt> which follows the log-format rules (see
Custom Log Format in section 8.2.4). This is particularly useful to pass
connection-specific information to the server (e.g. the client's SSL
certificate), or to combine several headers into one. This rule is not
final, so it is possible to add other similar rules. Note that header
addition is performed immediately, so one rule might reuse the resulting
header from a previous rule.
Não consigo entender como devo escrever o equivalente http-request add-header...
