Go to file

Sean McArthur 2a3844acc3 feat(client): enable CONNECT requests through the Client

While the upgrades feature enabled HTTP upgrades in both and the server and client, and the goal was for `CONNECT` requests to work as well, only the server could use them for `CONNECT`. The `Client` had some specific code rejecting `CONNECT` requests, and this removes it and prepares the `Client` to handle them correctly.

2018-06-22 21:00:28 -07: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(tests): change tests to use current_thread runtime

2018-06-18 12:30:56 -07:00

examples

doc(client): show spawning a client future, clarify lazy in client example

2018-06-18 17:02:57 -07:00

src

feat(client): enable CONNECT requests through the Client

2018-06-22 21:00:28 -07:00

tests

feat(client): enable CONNECT requests through the Client

2018-06-22 21:00:28 -07:00

.appveyor.yml

feat(lib): convert to use tokio 0.1

2018-03-19 11:43:47 -07:00

.gitignore

init

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

.travis.yml

chore(ci): skip building tests on minimum Rust version

2018-06-05 11:41:17 -07:00

Cargo.toml

feat(client): enable CONNECT requests through the Client

2018-06-22 21:00:28 -07:00

CHANGELOG.md

v0.12.2

2018-06-19 11:30:05 -07: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(lib): update description of hyper

2018-06-01 15:22:53 -07:00

README.md

hyper

A fast and correct 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.