mirrors/haproxy
1
0
Fork 0
mirror of https://git.haproxy.org/git/haproxy.git/ synced 2025-11-29 06:40:59 +01:00
Code Issues Projects Releases Wiki Activity

DOC: config: Add a note about conflict with ALPN/NPN settings and proto keyword

Browse Source 
If a mux protocol is forced and an incompatible ALPN or NPN settings are
used, connection errors may be experienced. There is no check performed
during HAProxy startup and It is not necessarily obvious. So a note is added
to warn users about this usage.
This commit is contained in:
Christopher Faulet 2025-11-20 16:05:01 +01:00
parent 0a7f3954b5
commit a14b7790ad
1 changed files with 17 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

19
doc/configuration.txt
View File

@ -17257,14 +17257,19 @@ proto <name>
Here are the protocols that may be used as argument to a "proto" directive on Here are the protocols that may be used as argument to a "proto" directive on
a bind line : a bind line :
quic : mode=HTTP side=FE|BE mux=QUIC flags=HTX|NO_UPG|FRAMED
h2 : mode=HTTP side=FE|BE mux=H2 flags=HTX|HOL_RISK|NO_UPG h2 : mode=HTTP side=FE|BE mux=H2 flags=HTX|HOL_RISK|NO_UPG
h1 : mode=HTTP side=FE|BE mux=H1 flags=HTX|NO_UPG h1 : mode=HTTP side=FE|BE mux=H1 flags=HTX|NO_UPG
none : mode=TCP side=FE|BE mux=PASS flags=NO_UPG none : mode=TCP side=FE|BE mux=PASS flags=NO_UPG
Idea behind this option is to bypass the selection of the best multiplexer's Idea behind this option is to bypass the selection of the best multiplexer's
protocol for all connections instantiated from this listening socket. For protocol for all connections instantiated from this listening socket. For
instance, it is possible to force the http/2 on clear TCP by specifying "proto instance, it is possible to force the http/2 on clear TCP by specifying
h2" on the bind line. "proto h2" on the bind line.
If the ALPN or the NPN settings are configured, the specified protocols
should be compatible with the multiplexer's protocol to avoid any issue. For
instance, if "proto h1" is set, the ALPN should not be set to "h2".
quic-cc-algo { cubic | newreno | bbr | nocc }[(<args,...>)] quic-cc-algo { cubic | newreno | bbr | nocc }[(<args,...>)]
This is a QUIC specific setting to select the congestion control algorithm This is a QUIC specific setting to select the congestion control algorithm
@ -17921,11 +17926,16 @@ check-proto <name>
h1 : mode=HTTP side=FE|BE mux=H1 flags=HTX|NO_UPG h1 : mode=HTTP side=FE|BE mux=H1 flags=HTX|NO_UPG
none : mode=TCP side=FE|BE mux=PASS flags=NO_UPG none : mode=TCP side=FE|BE mux=PASS flags=NO_UPG
quic : mode=HTTP side=FE|BE mux=QUIC flags=HTX|NO_UPG|FRAMED quic : mode=HTTP side=FE|BE mux=QUIC flags=HTX|NO_UPG|FRAMED
spop : mode=SPOP side=BE mux=SPOP flags=HOL_RISK|NO_UPG
Idea behind this option is to bypass the selection of the best multiplexer's Idea behind this option is to bypass the selection of the best multiplexer's
protocol for health-check connections established to this server. protocol for health-check connections established to this server.
If not defined, the server one will be used, if set. If not defined, the server one will be used, if set.
If the ALPN or the NPN settings are configured, the specified protocols
should be compatible with the multiplexer's protocol to avoid any issue. For
instance, if "proto h1" is set, the ALPN should not be set to "h2".
QUIC check configuration is not fully implemented yet. First, QUIC checks may QUIC check configuration is not fully implemented yet. First, QUIC checks may
only be performed for QUIC servers. Second, if one or more check specific only be performed for QUIC servers. Second, if one or more check specific
connection parameters is specified on a QUIC server, check protocol will connection parameters is specified on a QUIC server, check protocol will
@ -18791,10 +18801,15 @@ proto <name>
fcgi : mode=HTTP side=BE mux=FCGI flags=HTX|HOL_RISK|NO_UPG fcgi : mode=HTTP side=BE mux=FCGI flags=HTX|HOL_RISK|NO_UPG
h1 : mode=HTTP side=FE|BE mux=H1 flags=HTX|NO_UPG h1 : mode=HTTP side=FE|BE mux=H1 flags=HTX|NO_UPG
none : mode=TCP side=FE|BE mux=PASS flags=NO_UPG none : mode=TCP side=FE|BE mux=PASS flags=NO_UPG
spop : mode=SPOP side=BE mux=SPOP flags=HOL_RISK|NO_UPG
Idea behind this option is to bypass the selection of the best multiplexer's Idea behind this option is to bypass the selection of the best multiplexer's
protocol for all connections established to this server. protocol for all connections established to this server.
If the ALPN or the NPN settings are configured, the specified protocols
should be compatible with the multiplexer's protocol to avoid any issue. For
instance, if "proto h1" is set, the ALPN should not be set to "h2".
See also "ws" to use an alternative protocol for websocket streams. See also "ws" to use an alternative protocol for websocket streams.
redir <prefix> redir <prefix>