RFC 7230
An IETF specification document for the HTTP/1.1 protocol that defines message syntax and routing rules.
Timeline (last 90 days)
HTTP/1.1 connection reuse determination involves dimensions such as whether the response carries Content-Length or uses Transfer-Encoding: chunked, whether the status code is 204/304, and whether the request method is CONNECT or Upgrade.
The boundary determination corrected in Go 1.27 makes the client's conclusion about whether a connection can be safely returned to the idle pool more consistent with the normative wording of RFC 7230.
The HTTP/1.1 specification (RFC 7230) stipulates that request header field names are case-insensitive.
All Facts (3)
HTTP/1.1 connection reuse determination involves dimensions such as whether the response carries Content-Length or uses Transfer-Encoding: chunked, whether the status code is 204/304, and whether the request method is CONNECT or Upgrade.
50%UnverifiedThe boundary determination corrected in Go 1.27 makes the client's conclusion about whether a connection can be safely returned to the idle pool more consistent with the normative wording of RFC 7230.
50%UnverifiedThe HTTP/1.1 specification (RFC 7230) stipulates that request header field names are case-insensitive.
50%