Joe Wilm c32d0e9adf fix(http): stackoverflow in Conn::ready ...

I've had a couple of instances during stress testing now where
Conn::ready would overflow its stack due to recursing on itself. This
moves subsequent calls to ready() into a loop outside the function.

2016-10-06 18:02:26 -07:00

..

client

fix(http): stackoverflow in Conn::ready

2016-10-06 18:02:26 -07:00

header

feat(headers): add Warning header

2016-09-05 14:35:48 -04:00

http

fix(http): stackoverflow in Conn::ready

2016-10-06 18:02:26 -07:00

server

fix(http): stackoverflow in Conn::ready

2016-10-06 18:02:26 -07:00

error.rs

refactor(error): export url::ParseError in hyper's error module

2016-09-22 15:39:36 -07:00

lib.rs

docs(guide): adjust styles of the guides

2016-07-26 08:55:08 -07:00

method.rs

docs(*): fix typos, Markdown inconsistencies, and stutter

2016-05-20 11:42:29 -03:00

mock.rs

feat(lib): switch to non-blocking (asynchronous) IO

2016-05-16 09:51:18 -07:00

net.rs

feat(server): Server::new can take one or more listeners

2016-07-18 15:32:38 -07:00

status.rs

feat(lib): switch to non-blocking (asynchronous) IO

2016-05-16 09:51:18 -07:00

uri.rs

feat(server): add path() and query() to Request

2016-08-29 13:45:38 -07:00

version.rs

feat(lib): switch to non-blocking (asynchronous) IO

2016-05-16 09:51:18 -07:00