Connection Close on 204 No Content about fasthttp HOT 2 CLOSED

Apparently it has to do with with fasthttp detecting Transfer-Encoding: identity as default when no Content-Length is set and forcing connection close.
Its curious though that the server is responding a 204 which should skip body according to spec.
This is true when reading body, but not considered when parsing headers:
https://github.com/valyala/fasthttp/blob/master/header.go#L1421
https://github.com/valyala/fasthttp/blob/master/header.go#L1469

Changing default content-length to 0 fixes this issue, and seems to be the default behavior of other http clients.

Also, as per [rfc7230)(https://tools.ietf.org/html/rfc7230):

The "identity" transfer coding token has been removed.

A server MUST NOT send a Content-Length header field in any response
with a status code of 1xx (Informational) or 204 (No Content). A
server MUST NOT send a Content-Length header field in any 2xx
(Successful) response to a CONNECT request (Section 4.3.6 of
[RFC7231]).

from fasthttp.

Thanks for the bug report and the patch. I'll look into it tomorrow.

from fasthttp.