Releases: hyperium/h2
Releases Β· hyperium/h2
v0.3.14
- Add
Error::is_reset
function. - Bump MSRV to Rust 1.56.
- Return
RST_STREAM(NO_ERROR)
when the server early responds.
New Contributors
- @djkoloski made their first contribution in #616
- @bruceg made their first contribution in #618
- @ryanrussell made their first contribution in #620
- @kckeiks made their first contribution in #625
- @erebe made their first contribution in #634
v0.3.13
- Update private internal
tokio-util
dependency.
v0.3.12
- Avoid time operations that can panic (#599)
- Bump MSRV to Rust 1.49 (#606)
- Fix header decoding error when a header name is contained at a continuation
header boundary (#589) - Remove I/O type names from handshake
tracing
spans (#608)
New Contributors
- @LPardue made their first contribution in #602
- @hikaricai made their first contribution in #589
v0.3.11
v0.3.10
- Add
Error::is_go_away()
andError::is_remote()
methods. - Fix panic if receiving malformed PUSH_PROMISE with stream ID of 0.
v0.3.9
- Fix hang related to new
max_send_buffer_size
.
v0.3.8
- Add "extended CONNECT support". Adds
h2::ext::Protocol
, which is used for request and response extensions to connect new protocols over an HTTP/2 stream. - Add
max_send_buffer_size
options to client and server builders, and a default of ~400KB. This acts like a high-water mark for thepoll_capacity()
method. - Fix panic if receiving malformed HEADERS with stream ID of 0.
v0.3.7
- Fix panic if server sends a malformed frame on a stream client was about to open.
- Fix server to treat
:status
in a request as a stream error instead of connection error.
v0.3.6
- Fix regression of
h2::Error
that were created viaFrom<h2::Reason>
not returning their reason code inError::reason()
.
v0.3.5
- Fix sending of very large headers. Previously when a single header was too big to fit in a single
HEADERS
frame, an error was returned. Now it is broken up and sent correctly. - Fix buffered data field to be a bigger integer size.
- Refactor error format to include what initiated the error (remote, local, or user), if it was a stream or connection-level error, and any received debug data.