tree 72eddd6041a8fea3254ae2412d06b1ad1b19ddfb
parent a9e1c4c7c27b892b6b4f13ff0d0a96508970d2a9
author Christopher Faulet <cfaulet@haproxy.com> 1587041406 +0200
committer Christopher Faulet <cfaulet@haproxy.com> 1587976867 +0200

MAJOR: checks: Use the best mux depending on the protocol for health checks

When a tcp-check connect rule is evaluated, the mux protocol corresponding to
the health-check is chosen. So for TCP based health-checks, the mux-pt is
used. For HTTP based health-checks, the mux-h1 is used. The connection is marked
as private to be sure to not ruse regular HTTP connection for
health-checks. Connections reuse will be evaluated later.

The functions evaluating HTTP send rules and expect rules have been updated to
be HTX compliant. The main change for users is that HTTP health-checks are now
stricter on the HTTP message format. While before, the HTTP formatting and
parsing were minimalist, now messages should be well formatted.