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

HTTP/2 stream 1 was not closed cleanly: INTERNAL_ERROR (err 2) #166

Open
simonjoom opened this issue Dec 12, 2017 · 2 comments
Open

HTTP/2 stream 1 was not closed cleanly: INTERNAL_ERROR (err 2) #166

simonjoom opened this issue Dec 12, 2017 · 2 comments

Comments

@simonjoom
Copy link

i ve got this error with http/2 when testing blocking curl
curl -A "80legs" http://yourdomain.com

HTTP/2 stream 1 was not closed cleanly: INTERNAL_ERROR (err 2)

is it an error or a normal output?

@mitchellkrogza
Copy link
Collaborator

mitchellkrogza commented Dec 13, 2017 via email

@simonjoom
Copy link
Author

simonjoom commented Dec 13, 2017

ok
But i think it's due from http/2
nghttp2/nghttp2#746

did you test your code using http/2 instead http/1 with ssl?

For the record, sending Content-Length: 0 with 204 status code is a violation against RFC 7230 (See https://tools.ietf.org/html/rfc7230#section-3.3.2). We implemented this in nghttp2 v1.17.0. But user reported that some widely used service sends Content-Length:0 with 204 code (#735).
We workaround this by simply discarding such header field in upcoming nghttp2 v1.18.0.

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

No branches or pull requests

2 participants