Releases: tokio-rs/axum
Releases · tokio-rs/axum
axum-core - v0.2.6
- change: axum-core's MSRV is now 1.56 (#1098)
axum - v0.5.7
axum-extra - v0.3.4
axum-core - v0.2.5
axum-macros - v0.2.2
- added: In
debug_handler
, check ifRequest
is used as non-final extractor (#1035) - added: In
debug_handler
, check if multiplePath
extractors are used (#1035) - added: In
debug_handler
, check if multiple body extractors are used (#1036) - added: Support customizing rejections for
#[derive(TypedPath)]
(#1012)
axum-extra - v0.3.3
axum - v0.5.6
- added: Add
WebSocket::protocol
to return the selected WebSocket subprotocol, if there is one. (#1022) - fixed: Improve error message for
PathRejection::WrongNumberOfParameters
to hint at using
Path<(String, String)>
orPath<SomeStruct>
(#1023) - fixed:
PathRejection::WrongNumberOfParameters
now uses500 Internal Server Error
since
it's a programmer error and not a client error (#1023) - fixed: Fix
InvalidFormContentType
mentioning the wrong content type
axum-extra - v0.3.2
- added: Add
extract::Form
which supports multi-value items (#1031)
axum - v0.5.5
- fixed: Correctly handle
GET
,HEAD
, andOPTIONS
requests inContentLengthLimit
.
Request with these methods are now accepted if they do not have aContent-Length
header, and
the request body will not be checked. If they do have aContent-Length
header they'll be
rejected. This allowsContentLengthLimit
to be used as middleware around several routes,
includingGET
routes (#989) - added: Add
MethodRouter::{into_make_service, into_make_service_with_connect_info}
(#1010)