mirror of
https://git.haproxy.org/git/haproxy.git/
synced 2026-01-15 13:51:00 +01:00
75dd2b7987
It seems it was a bad idea to use the same function as for TCP ssl sockets to initialize the SSL session objects for QUIC with ssl_bio_and_sess_init(). Indeed, this had as very bad side effects to generate SSL errors due to the fact that such BIOs initialized for QUIC could not finally be controlled via the BIO_ctrl*() API, especially BIO_ctrl() function used by very much other internal OpenSSL functions (BIO_push(), BIO_pop() etc). Others OpenSSL base QUIC implementation do not use at all BIOs to configure QUIC connections. So, we decided to proceed the same way as ngtcp2 for instance: only initialize an SSL object and call SSL_set_quic_method() to set its underlying method. Note that calling this function silently disable this option: SSL_OP_ENABLE_MIDDLEBOX_COMPAT. We implement qc_ssl_sess_init() to initialize SSL sessions for QUIC connections to do so with a retry in case of allocation failure as this is done by ssl_bio_and_sess_init(). We also modify the code part for haproxy servers.
The HAProxy documentation has been split into a number of different files for ease of use. Please refer to the following files depending on what you're looking for : - INSTALL for instructions on how to build and install HAProxy - BRANCHES to understand the project's life cycle and what version to use - LICENSE for the project's license - CONTRIBUTING for the process to follow to submit contributions The more detailed documentation is located into the doc/ directory : - doc/intro.txt for a quick introduction on HAProxy - doc/configuration.txt for the configuration's reference manual - doc/lua.txt for the Lua's reference manual - doc/SPOE.txt for how to use the SPOE engine - doc/network-namespaces.txt for how to use network namespaces under Linux - doc/management.txt for the management guide - doc/regression-testing.txt for how to use the regression testing suite - doc/peers.txt for the peers protocol reference - doc/coding-style.txt for how to adopt HAProxy's coding style - doc/internals for developer-specific documentation (not all up to date)