5c88b9fcfb
This patch impacts only the haproxy builds against aws-lc TLS stack (USE_OPENSSL_AWSLC). As mentionned by the boringssl documentation, SSL_do_handshake() completes as soon as ClientHello is processed and server flight sent (from the TLS stack to the server endpoint I guess). Into QUIC, the completion has as side effect to discard the Handshake packet number space. If this handshake completion is not deffered, the Handshake level CRYPTO data will not be sent to the peer (because of the assotiated packet number space discarding). According to the documentation, SSL_in_early_data() may be used to do that. If it returns 1, this means that the handshake is still in progress but has enough progressed to send half-RTT data. This patch is required to make the haproxy builds against aws-lc TLS stack support 0-RTT.
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)