Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

HttpTooLargeError after the response #437

Closed
mikedilger opened this issue Apr 6, 2015 · 1 comment · Fixed by #455
Closed

HttpTooLargeError after the response #437

mikedilger opened this issue Apr 6, 2015 · 1 comment · Fixed by #455

Comments

@mikedilger
Copy link
Contributor

Ever since the new buffering code, I get HttpTooLargeErrors after almost every response. It is after the handler returns and the response has been sent, and so the site continues to function. But clearly something is amiss. The requests are rather normal small requests, nothing large, nothing fancy.

ERROR:hyper::server: request error = HttpTooLargeError

in server/mod.rs handle_connection() while keep_alive loop, the Request::new() calls http::parse_request() which fails with HttpTooLargeError at some point around this keep_alive loop, which means that read_into_buf() must have returned Ok(0) which means that self.cap < v.capacity(), but I haven't looked further as to why that is for small requests that are only handled once.

@hoxnox
Copy link

hoxnox commented Apr 15, 2015

I maked a pull request: #454

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants