…#3700)

There is currently no way to write to ReadBufCursor without
unsafe code, even though writing a slice to it like one would
do to a Buf shouldn't require unsafe code.

…#3712)

The Service trait now includes a note about the behavior of returning an Error to a hyper server, which can cause the connection to be abruptly aborted depending on the protocol. This information is important for developers working with hyper servers.

Before this patch, the option was not fully propagated to the inner server conn state object. Now it is.

Signed-off-by: friendlyping <friendlyping@icloud.com>

…ax_concurrent_streams()` (#3731)

When reading the documentation for `Connection` it is not entirely
obvious how instances of this type are obtained. Add a helpful link,
mostly for those less familiar.

…ts (#3748)

s

Co-authored-by: Sean McArthur <sean@seanmonstar.com>

cc #3568

)

This includes conditions where hyper knows the connection will end after the response, such as a request error that ruins the connection, or when graceful shutdown is triggered.

Closes #3720

If request headers are received in incremental partial chunks, hyper
would restart parsing each time. This is because the HTTP/1 parser is
stateless, since the most common case is a full message and stateless
parses faster.

However, if continuing to receive more partial chunks of the request,
each subsequent full parse is slower and slower. Since partial parses is
less common, we can store a little bit of state to improve performance
in general.

Now, if a partial request is received, hyper will check for the end of
the message quickly, and if not found, simply save the length to allow
the next partial chunk to start its search from there. Only once the end
is found will a fill parse happen.

Reported-by: Datong Sun <datong.sun@konghq.com>