Go to file

Sean McArthur dc619a8fa0 fix(client): detect connection closes as pool tries to use

Currently, if the remote closes the connection at the same time that the
pool selects it to use for a new request, the connection may actually
hang. This fix will now more allow the keep-alive read to check the
socket even when the `Conn` think it's busy.

If the connection was closed before the request write happened, returns
back an `Error::Cancel`, letting the user know they could safely retry
it.

Closes #1439

2018-02-12 18:16:21 -08:00

.github

chore(github): remove note about commit message style in PR template

2017-11-08 16:35:55 -08:00

.travis

chore(ci): only publish master docs

2017-06-16 13:06:46 -07:00

benches

perf(http): utilize writev when possible

2018-01-25 14:02:11 -08:00

examples

docs(example): fix send file to only send range of buffer read into

2018-01-16 11:52:56 -08:00

src

fix(client): detect connection closes as pool tries to use

2018-02-12 18:16:21 -08:00

tests

fix(client): detect connection closes as pool tries to use

2018-02-12 18:16:21 -08:00

.appveyor.yml

chore(ci): update appveyor to use stable instead of nightly

2017-06-08 13:43:43 -07:00

.gitignore

init

2014-08-30 14:18:28 -07:00

.travis.yml

chore(ci): update CI minimum Rust to 1.18 (because mio)

2018-01-09 15:53:06 -08:00

Cargo.toml

v0.11.18

2018-02-07 13:59:47 -08:00

CHANGELOG.md

v0.11.18

2018-02-07 13:59:47 -08:00

CONTRIBUTING.md

docs(contributing): add link to easy issues

2017-10-09 09:22:01 -07:00

LICENSE

init

2014-08-30 14:18:28 -07:00

README.md

docs(README): "1.0 milestone" => "milestones"

2018-01-26 12:34:05 -08:00

README.md

hyper

A low-level HTTP implementation for Rust.

Get started by looking over the guides.

Overview

hyper is a fast, safe HTTP implementation written in and for Rust.

hyper offers both an HTTP client and server which can be used to drive complex web applications written entirely in Rust.

hyper makes use of "async IO" (non-blocking sockets) via the Tokio and Futures crates.

Be aware that hyper is still actively evolving towards 1.0, and is likely to experience breaking changes before stabilising. You can also see the issues in the upcoming milestones.