dec23dc43f
These two commands use distinct parse/release functions but a common iohandler, thus they need to keep the same context. It was created under the name "commit_cacrlfile_ctx" and holds a large part of the pointers (6) and the ca_type field that helps distinguish between the two commands for the I/O handler. It looks like some of these fields could have been merged since apparently the CA part only uses *cafile* and the CRL part *crlfile*, while both old and new are of type cafile_entry and set only for each type. This could probably even simplify some parts of the code that tries to use the correct field. These fields were the last ones to be migrated thus the appctx's ssl context could finally be removed.
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)