d8b34459b5
On frontend side, H3 layer transcodes HTX status code into HTTP/3 HEADERS frame. This is done by calling qpack_encode_int_status(). Prior to this patch, the latter function was also responsible to reject an invalid value, which guarantee that only valid codes are encoded (between 100 and 999 values). However, this is not practical as it is impossible to differentiate between an invalid code error and a buffer room exhaustation. Changes this so that now HTTP/3 layer first ensures that HTX code is valid. The stream is closed with H3_INTERNAL_ERROR if invalid value is present. Thus, qpack_encode_int_status() will only report an error due to buffer room exhaustion. If a small buffer is used, a standard buffer will be reallocated which should be sufficient to encode the response. The impact of this bug is minimal. Its main benefit is code clarity, while also removing an unnecessary realloc when confronting with an invalid HTTP code. This should be backported at least up to 3.1. Prior to it, smallbuf mechanism isn't present, hence the impact of this patch is less important. However, it may still be backported to older versions, which should facilitate picking patches for HTTP 1xx interim response support. |
||
|---|---|---|
| .github | ||
| addons | ||
| admin | ||
| dev | ||
| doc | ||
| examples | ||
| include | ||
| reg-tests | ||
| scripts | ||
| src | ||
| tests | ||
| .cirrus.yml | ||
| .gitattributes | ||
| .gitignore | ||
| .mailmap | ||
| .travis.yml | ||
| BRANCHES | ||
| BSDmakefile | ||
| CHANGELOG | ||
| CONTRIBUTING | ||
| INSTALL | ||
| LICENSE | ||
| MAINTAINERS | ||
| Makefile | ||
| README.md | ||
| SUBVERS | ||
| VERDATE | ||
| VERSION | ||
HAProxy
HAProxy is a free, very fast and reliable reverse-proxy offering high availability, load balancing, and proxying for TCP and HTTP-based applications.
Installation
The INSTALL file describes how to build HAProxy. A list of packages is also available on the wiki.
Getting help
The discourse and the mailing-list are available for questions or configuration assistance. You can also use the slack or IRC channel. Please don't use the issue tracker for these.
The issue tracker is only for bug reports or feature requests.
Documentation
The HAProxy documentation has been split into a number of different files for ease of use. It is available in text format as well as HTML. The wiki is also meant to replace the old architecture guide.
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)
License
HAProxy is licensed under GPL 2 or any later version, the headers under LGPL 2.1. See the LICENSE file for a more detailed explanation.