e8ae99b111
Now we can build a series of data frames by reading from a file and chunking it into frames of requested length. It's mostly useful for data frames (e.g. post). One way to announce these upfront is to capture the output of curl use without content-length: $ nc -lp4446 > post-h2-nocl.bin $ curl -v --http2-prior-knowledge http://127.0.0.1:4446/url -H "content-length:" -d @/dev/null Then just change the 5th byte from the end from 1 to 0 to remove the end-of-stream bit, it will allow to chain a file, then to send an empty DATA frame with ES set : $ (dev/h2/mkhdr.sh -i 1 -t data -d CHANGELOG; dev/h2/mkhdr.sh -i 1 -t data -l 0 -f es) > h2-data-changelog.bin Then post that to the server: $ cat post-h2-nocl.bin h2-data-changelog.bin | nc 0 4446 |
||
|---|---|---|
| .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 | ||
README
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)