tree fa767de8dfe072757471e270da459e2953fccd4d
parent d20fdb0454981ebd071d9d805895a3cd510a1f27
author Christopher Faulet <cfaulet@haproxy.com> 1560499693 +0200
committer Christopher Faulet <cfaulet@haproxy.com> 1560503612 +0200

MINOR: htx: Add 3 flags on the start-line to deal with the request schemes

The first one, HTX_SL_F_HAS_SCHM, will be used to know the request has an
explicit scheme. So, in H2, it is always true because the pseudo-header
":scheme" is mandatory. In H1, it is only true when an absolute URI is found on
the start-line. The other flags, HTX_SL_F_SCHM_HTTP and HTX_SL_F_SCHM_HTTPS,
will be used to know which scheme the request have. For now, other protocols are
not handled.

The aim of these flags is to pass this information to the backend side in
general, and to the H2 mux in particular. So the multiplexer will have a chance
to use this information to send the right scheme to the server.