mirror of
https://github.com/curl/curl.git
synced 2024-11-27 05:50:21 +08:00
b9b50f3193
The current design of the Hyper integration requires rebuilding the Hyper clientconn for each request. However, building the clientconn requires resending the HTTP/2 connection preface, which is incorrect from a protocol perspective. That in turn causes servers to send GOAWAY frames, effectively degrading performance to "no connection reuse" in the best case. It may also be triggering some bugs where requests get dropped entirely and reconnects take too long. This doesn't rule out HTTP/2 support with Hyper, but it may take a redesign of the Hyper integration in order to make things work. Closes #12191 |
||
---|---|---|
.. | ||
cmdline-opts | ||
examples | ||
libcurl | ||
.gitignore | ||
ALTSVC.md | ||
BINDINGS.md | ||
BUFQ.md | ||
BUFREF.md | ||
BUG-BOUNTY.md | ||
BUGS.md | ||
CHECKSRC.md | ||
CIPHERS.md | ||
CMakeLists.txt | ||
CODE_OF_CONDUCT.md | ||
CODE_REVIEW.md | ||
CODE_STYLE.md | ||
CONNECTION-FILTERS.md | ||
CONTRIBUTE.md | ||
curl-config.1 | ||
CURL-DISABLE.md | ||
DEPRECATE.md | ||
DYNBUF.md | ||
EARLY-RELEASE.md | ||
EXPERIMENTAL.md | ||
FAQ | ||
FEATURES.md | ||
GOVERNANCE.md | ||
HELP-US.md | ||
HISTORY.md | ||
HSTS.md | ||
HTTP2.md | ||
HTTP3.md | ||
HTTP-COOKIES.md | ||
HYPER.md | ||
INSTALL | ||
INSTALL.cmake | ||
INSTALL.md | ||
INTERNALS.md | ||
IPFS.md | ||
KNOWN_BUGS | ||
MAIL-ETIQUETTE | ||
Makefile.am | ||
MANUAL.md | ||
mk-ca-bundle.1 | ||
MQTT.md | ||
NEW-PROTOCOL.md | ||
options-in-versions | ||
PARALLEL-TRANSFERS.md | ||
README.md | ||
RELEASE-PROCEDURE.md | ||
ROADMAP.md | ||
RUSTLS.md | ||
SECURITY-ADVISORY.md | ||
SSL-PROBLEMS.md | ||
SSLCERTS.md | ||
THANKS | ||
THANKS-filter | ||
TheArtOfHttpScripting.md | ||
TODO | ||
URL-SYNTAX.md | ||
VERSIONS.md | ||
VULN-DISCLOSURE-POLICY.md | ||
WEBSOCKET.md |
Documentation
you will find a mix of various documentation in this directory and subdirectories, using several different formats. Some of them are not ideal for reading directly in your browser.
If you would rather see the rendered version of the documentation, check out the curl website's documentation section for general curl stuff or the libcurl section for libcurl related documentation.