mirror of
http://git.haproxy.org/git/haproxy.git/
synced 2024-12-26 06:32:13 +00:00
haproxy public development tree
7838a79bac
All functions of the h2 data path were updated to receive one or multiple TRACE() calls, at least one pair of TRACE_ENTER()/TRACE_LEAVE(), and those manipulating protocol elements have been improved to report frame types, special state transitions or detected errors. Even with careful tests, no performance impact was measured when traces are disabled. They are not completely exploited yet, the callback function tries to dump a lot about them, but still doesn't provide buffer dumps, nor does it indicate the stream or connection error codes. The first argument is always set to the connection when known. The second argument is set to the h2s when known, sometimes a 3rd argument is set to a buffer, generally the rxbuf or htx, and occasionally the 4th argument points to an integer (number of bytes read/sent, error code). Retrieving a 10kB object produces roughly 240 lines when at developer level, 35 lines at data level, 27 at state level, and 10 at proto level and 2 at user level. For now the headers are not dumped, but the start line are emitted in each direction at user level. The patch is marked medium because it touches lots of places, though it takes care not to change the execution path. |
||
|---|---|---|
| .github/ISSUE_TEMPLATE | ||
| contrib | ||
| doc | ||
| ebtree | ||
| examples | ||
| include | ||
| reg-tests | ||
| scripts | ||
| src | ||
| tests | ||
| .cirrus.yml | ||
| .gitignore | ||
| .travis.yml | ||
| BRANCHES | ||
| CHANGELOG | ||
| CONTRIBUTING | ||
| INSTALL | ||
| LICENSE | ||
| MAINTAINERS | ||
| Makefile | ||
| README | ||
| ROADMAP | ||
| SUBVERS | ||
| VERDATE | ||
| VERSION | ||
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)