mirror of
https://github.com/haproxy/haproxy.git
synced 2026-02-19 02:29:31 -05:00
HAProxy - Load balancer
f43f36da5b
As reported by Dominik Froehlich in github issue #1968, some H2 request parsing errors do not result in a log being emitted. This is annoying for debugging because while an RST_STREAM is correctly emitted to the client, there's no way without enabling traces to find it on the haproxy side. After some testing with various abnormal requests, a few places were found where logs were missing and could be added. In this case, we simply use sess_log() so some sample fetch functions might not be available since the stream is not created. But at least there will be a BADREQ in the logs. A good eaxmple of this consists in sending forbidden headers or header syntax (e.g. presence of LF in value). Some quick tests can be done this way: - protocol error (LF in value): curl -iv --http2-prior-knowledge -H "$(printf 'a:b\na')" http://0:8001/ - too large header block after decoding: curl -v --http2-prior-knowledge -H "a:$(perl -e "print('a'x10000)")" -H "a:$(perl -e "print('a'x10000)")" http://localhost:8001/ This should be backported where needed, most likely 2.7 and 2.6 at least for a start, and progressively to other versions. |
||
|---|---|---|
| .github | ||
| addons | ||
| admin | ||
| dev | ||
| doc | ||
| examples | ||
| include | ||
| reg-tests | ||
| scripts | ||
| src | ||
| tests | ||
| .cirrus.yml | ||
| .gitattributes | ||
| .gitignore | ||
| .mailmap | ||
| .travis.yml | ||
| BRANCHES | ||
| CHANGELOG | ||
| CONTRIBUTING | ||
| INSTALL | ||
| LICENSE | ||
| MAINTAINERS | ||
| Makefile | ||
| README | ||
| 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)