nginx-badbot-blocker icon indicating copy to clipboard operation
nginx-badbot-blocker copied to clipboard

Published 20 hours ago • verified publisher icon mariusv

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

Open simonjoom opened this issue 7 years ago • 2 comments

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?

simonjoom avatar Dec 12 '17 20:12 simonjoom

That’s a problem with your ssl configuration. That’s not the blocker doing that.

mitchellkrogza avatar Dec 13 '17 06:12 mitchellkrogza

ok But i think it's due from http/2 https://github.com/nghttp2/nghttp2/issues/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.

simonjoom avatar Dec 13 '17 09:12 simonjoom