Go to file

Sean McArthur 36e66a5054 fix(lib): properly handle HTTP/1.0 remotes

- Downgrades internal semantics to HTTP/1.0 if peer sends a message with
  1.0 version.
- If downgraded, chunked writers become EOF writers, with the connection
  closing once the writing is complete.
- When downgraded, if keep-alive was wanted, the `Connection: keep-alive`
  header is added.

Closes #1304

2018-01-22 10:08:27 -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

chore(benches): remove unused pretty_env_logger import

2017-08-28 15:11:52 -07: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(lib): properly handle HTTP/1.0 remotes

2018-01-22 10:08:27 -08:00

tests

fix(lib): properly handle HTTP/1.0 remotes

2018-01-22 10:08:27 -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

chore(depenencies): update pretty-env-logger to 0.2

2018-01-19 17:37:34 -08:00

CHANGELOG.md

v0.11.14

2018-01-16 14:20:26 -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): make docs badges more consistent

2017-11-03 17:02:56 +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 1.0 issue milestone.