in haproxy -vv. The protocols properties are reported : the mode (TCP/HTTP),
the side (FE/BE), the mux name and its flags.
- Some protocols report errors on aborts (flag=CLEAN_ABRT). Some others are
- subject to the head-of-line blocking on server side (flag=HOL_RISK). Finally
- some protocols don't support upgrades (flag=NO_UPG). The HTX compatibility is
- also reported (flag=HTX).
+ Some protocols are subject to the head-of-line blocking on server side
+ (flag=HOL_RISK). Finally some protocols don't support upgrades (flag=NO_UPG).
+ The HTX compatibility is also reported (flag=HTX).
Here are the protocols that may be used as argument to a "proto" directive on
a bind line :
- h2 : mode=HTTP side=FE|BE mux=H2 flags=HTX|CLEAN_ABRT|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
none : mode=TCP side=FE|BE mux=PASS flags=NO_UPG
protocols is reported in haproxy -vv. The protocols properties are
reported : the mode (TCP/HTTP), the side (FE/BE), the mux name and its flags.
- Some protocols report errors on aborts (flag=CLEAN_ABRT). Some others are
- subject to the head-of-line blocking on server side (flag=HOL_RISK). Finally
- some protocols don't support upgrades (flag=NO_UPG). The HTX compatibility is
- also reported (flag=HTX).
+ Some protocols are subject to the head-of-line blocking on server side
+ (flag=HOL_RISK). Finally some protocols don't support upgrades (flag=NO_UPG).
+ The HTX compatibility is also reported (flag=HTX).
Here are the protocols that may be used as argument to a "check-proto"
directive on a server line:
- h2 : mode=HTTP side=FE|BE mux=H2 flags=HTX|CLEAN_ABRT|HOL_RISK|NO_UPG
+ h2 : mode=HTTP side=FE|BE mux=H2 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
none : mode=TCP side=FE|BE mux=PASS flags=NO_UPG
reported in haproxy -vv.The protocols properties are reported : the mode
(TCP/HTTP), the side (FE/BE), the mux name and its flags.
- Some protocols report errors on aborts (flag=CLEAN_ABRT). Some others are
- subject to the head-of-line blocking on server side (flag=HOL_RISK). Finally
- some protocols don't support upgrades (flag=NO_UPG). The HTX compatibility is
- also reported (flag=HTX).
+ Some protocols are subject to the head-of-line blocking on server side
+ (flag=HOL_RISK). Finally some protocols don't support upgrades (flag=NO_UPG).
+ The HTX compatibility is also reported (flag=HTX).
Here are the protocols that may be used as argument to a "proto" directive on
a server line :
- h2 : mode=HTTP side=FE|BE mux=H2 flags=HTX|CLEAN_ABRT|HOL_RISK|NO_UPG
+ h2 : mode=HTTP side=FE|BE mux=H2 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
none : mode=TCP side=FE|BE mux=PASS flags=NO_UPG
/* MUX-specific flags */
enum {
MX_FL_NONE = 0x00000000,
- MX_FL_CLEAN_ABRT = 0x00000001, /* abort is clearly reported as an error */
- MX_FL_HTX = 0x00000002, /* set if it is an HTX multiplexer */
- MX_FL_HOL_RISK = 0x00000004, /* set if the protocol is subject the to head-of-line blocking on server */
- MX_FL_NO_UPG = 0x00000008, /* set if mux does not support any upgrade */
+ MX_FL_HTX = 0x00000001, /* set if it is an HTX multiplexer */
+ MX_FL_HOL_RISK = 0x00000002, /* set if the protocol is subject the to head-of-line blocking on server */
+ MX_FL_NO_UPG = 0x00000004, /* set if mux does not support any upgrade */
};
/* PROTO token registration */