* Copy over changelogs from v0.4.x branch Preparing to release 0.5 * bump crate versions
35 KiB
Changelog
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.
Unreleased
-
added: Document sharing state between handler and middleware (#783)
-
added:
Extension<_>can now be used in tuples for building responses, and will set an extension on the response (#797) -
added:
extract::Hostfor extracting the hostname of a request (#827) -
added: Add
IntoResponsePartstrait which allows defining custom response types for adding headers or extensions to responses (#797) -
added:
TypedHeaderimplements the newIntoResponsePartstrait so they can be returned from handlers as parts of a response (#797) -
changed:
Router::mergenow acceptsInto<Router>(#819) -
breaking:
sse::Eventnow accepts types implementingAsRef<str>instead ofInto<String>as field values. -
breaking:
sse::Eventnow panics if a setter method is called twice instead of silently overwriting old values. -
breaking: Require
Output = ()onWebSocketStream::on_upgrade(#644) -
breaking: Make
TypedHeaderRejectionReason#[non_exhaustive](#665) -
breaking: Using
HeaderMapas an extractor will no longer remove the headers and thus they'll still be accessible to other extractors, such asaxum::extract::Json. InsteadHeaderMapwill clone the headers. You should prefer to useTypedHeaderto extract only the headers you need (#698)This includes these breaking changes:
RequestParts::take_headershas been removed.RequestParts::headersreturns&HeaderMap.RequestParts::headers_mutreturns&mut HeaderMap.HeadersAlreadyExtractedhas been removed.- The
HeadersAlreadyExtractedvariant has been removed from these rejections:RequestAlreadyExtractedRequestPartsAlreadyExtractedJsonRejectionFormRejectionContentLengthLimitRejectionWebSocketUpgradeRejection
<HeaderMap as FromRequest<_>>::Rejectionhas been changed tostd::convert::Infallible.
-
breaking:
axum::http::Extensionsis no longer an extractor (ie it doesn't implementFromRequest). Theaxum::extract::Extensionextractor is not impacted by this and works the same. This change makes it harder to accidentally remove all extensions which would result in confusing errors elsewhere (#699) This includes these breaking changes:RequestParts::take_extensionshas been removed.RequestParts::extensionsreturns&Extensions.RequestParts::extensions_mutreturns&mut Extensions.RequestAlreadyExtractedhas been removed.<Request as FromRequest>::Rejectionis nowBodyAlreadyExtracted.<http::request::Parts as FromRequest>::Rejectionis nowInfallible.ExtensionsAlreadyExtractedhas been removed.- The
ExtensionsAlreadyExtractedremoved variant has been removed from these rejections:ExtensionRejectionPathRejectionMatchedPathRejectionWebSocketUpgradeRejection
-
breaking:
Redirect::foundhas been removed (#800) -
breaking:
AddExtensionLayerhas been removed. UseExtensioninstead. It now implementstower::Layer(#807) -
breaking:
AddExtensionhas been moved from the root module tomiddleware -
breaking:
.nest("/foo/", Router::new().route("/bar", _))now does the right thing and results in a route at/foo/barinstead of/foo//bar(#824) -
breaking: Routes are now required to start with
/. Previously routes such as:foowould be accepted but most likely result in bugs (#823) -
breaking:
Headershas been removed. Arrays of tuples directly implementIntoResponsePartsso([("x-foo", "foo")], response)now works (#797) -
breaking:
InvalidJsonBodyhas been replaced withJsonDataErrorto clearly signal that the request body was syntactically valid JSON but couldn't be deserialized into the target type -
breaking:
Handleris no longer an#[async_trait]but instead has an associatedFuturetype. That allows users to build their ownHandlertypes without paying the cost of#[async_trait](#879) -
changed: New
JsonSyntaxErrorvariant added toJsonRejection. This is returned when the request body contains syntactically invalid JSON -
fixed: Correctly set the
Content-Lengthheader for response toHEADrequests (#734) -
fixed: Fix wrong
content-lengthforHEADrequests to endpoints that returns chunked responses (#755) -
fixed: Fixed several routing bugs related to nested "opaque" tower services (i.e. non-
Routerservices) (#841 and #842) -
changed: Update to tokio-tungstenite 0.17 (#791)
-
breaking:
Redirect::{to, temporary, permanent}now accept&strinstead ofUri(#889) -
breaking: Remove second type parameter from
Router::into_make_service_with_connect_infoandHandler::into_make_service_with_connect_infoto supportMakeServices that accept multiple targets (#892)
0.4.8 (2. March, 2022)
- Use correct path for
AddExtensionLayerandAddExtension::layerdeprecation notes (#812)
0.4.7 (1. March, 2022)
- added: Implement
tower::LayerforExtension(#801) - changed: Deprecate
AddExtensionLayer. UseExtensioninstead (#805)
0.4.6 (22. February, 2022)
- added:
middleware::from_fnfor creating middleware from async functions. This previously lived in axum-extra but has been moved to axum (#719) - fixed: Set
Allowheader when responding with405 Method Not Allowed(#733)
0.4.5 (31. January, 2022)
- Reference axum-macros instead of axum-debug. The latter has been superseded by axum-macros and is deprecated (#738)
0.4.4 (13. January, 2022)
- fixed: Fix using incorrect path prefix when nesting
Routers at/(#691) - fixed: Make
nest("", service)work and mean the same asnest("/", service)(#691) - fixed: Replace response code
301with308for trailing slash redirects. Also deprecatesRedirect::found(302) in favor ofRedirect::temporary(307) orRedirect::to(303). This is to prevent clients from changing non-GETrequests toGETrequests (#682)
0.4.3 (21. December, 2021)
- added:
axum::AddExtension::layer(#607) - added: Re-export the headers crate when the headers feature is active (#630)
- fixed:
sse::Eventwill no longer drop the leading space of data, event ID and name values that have it (#600) - fixed:
sse::Eventis more strict about what field values it supports, disallowing any SSE events that break the specification (such as field values containing carriage returns) (#599) - fixed: Improve documentation of
sse::Event(#601) - fixed: Make
Pathfail withExtensionsAlreadyExtractedif another extractor (such asRequest) has previously taken the request extensions. ThusPathRejectionnow contains a variant withExtensionsAlreadyExtracted. This is not a breaking change sincePathRejectionis marked as#[non_exhaustive](#619) - fixed: Fix misleading error message for
PathRejectionif extensions had previously been extracted (#619) - fixed: Use
AtomicU32internally, rather thanAtomicU64, to improve portability (#616)
0.4.2 (06. December, 2021)
- fix: Depend on the correct version of
axum-core(#592)
0.4.1 (06. December, 2021)
- added:
axum::response::Responsenow exists as a shorthand for writingResponse<BoxBody>(#590)
0.4.0 (02. December, 2021)
- breaking: New
MethodRouterthat works similarly toRouter:- Route to handlers and services with the same type
- Add middleware to some routes more easily with
MethodRouter::layerandMethodRouter::route_layer. - Merge method routers with
MethodRouter::merge - Customize response for unsupported methods with
MethodRouter::fallback
- breaking: The default for the type parameter in
FromRequestandRequestPartshas been removed. UseFromRequest<Body>andRequestParts<Body>to get the previous behavior (#564) - added:
FromRequestandIntoResponseare now defined in a new calledaxum-core. This crate is intended for library authors to depend on, rather thanaxumitself, if possible.axum-corehas a smaller API and will thus receive fewer breaking changes.FromRequestandIntoResponseare re-exported fromaxumin the same location so nothing is changed foraxumusers (#564) - breaking: The previously deprecated
axum::body::box_bodyfunction has been removed. Useaxum::body::boxedinstead. - fixed: Adding the same route with different methods now works ie
.route("/", get(_)).route("/", post(_)). - breaking:
routing::handler_method_routerandrouting::service_method_routerhas been removed in favor ofrouting::{get, get_service, ..., MethodRouter}. - breaking:
HandleErrorExthas been removed in favor ofMethodRouter::handle_error. - breaking:
HandleErrorLayernow requires the handler function to beasync(#534) - added:
HandleErrorLayernow supports running extractors. - breaking: The
Handler<B, T>trait is now defined asHandler<T, B = Body>. That is the type parameters have been swapped andBdefaults toaxum::body::Body(#527) - breaking:
Router::mergewill panic if both routers have fallbacks. Previously the left side fallback would be silently discarded (#529) - breaking:
Router::nestwill panic if the nested router has a fallback. Previously it would be silently discarded (#529) - Update WebSockets to use tokio-tungstenite 0.16 (#525)
- added: Default to return
charset=utf-8for text content type. (#554) - breaking: The
BodyandBodyErrorassociated types on theIntoResponsetrait have been removed - instead,.into_response()will now always returnResponse<BoxBody>(#571) - breaking:
PathParamsRejectionhas been renamed toPathRejectionand its variants renamed toFailedToDeserializePathParamsandMissingPathParams. This makes it more consistent with the rest of axum (#574) - added:
Path's rejection type now provides data about exactly which part of the path couldn't be deserialized (#574)
0.3.4 (13. November, 2021)
- change:
box_bodyhas been renamed toboxed.box_bodystill exists but is deprecated (#530)
0.3.3 (13. November, 2021)
- Implement
FromRequestforhttp::request::Partsso it can be used an extractor (#489) - Implement
IntoResponseforhttp::response::Parts(#490)
0.3.2 (08. November, 2021)
- added: Add
Router::route_layerfor applying middleware that will only run on requests that match a route. This is useful for middleware that return early, such as authorization (#474)
0.3.1 (06. November, 2021)
- fixed: Implement
CloneforIntoMakeServiceWithConnectInfo(#471)
0.3.0 (02. November, 2021)
- Overall:
-
fixed: All known compile time issues are resolved, including those with
boxedand those introduced by Rust 1.56 (#404) -
breaking: The router's type is now always
Routerregardless of how many routes or middleware are applied (#404)This means router types are all always nameable:
fn my_routes() -> Router { Router::new().route( "/users", post(|| async { "Hello, World!" }), ) } -
breaking: Added feature flags for HTTP1 and JSON. This enables removing a few dependencies if your app only uses HTTP2 or doesn't use JSON. This is only a breaking change if you depend on axum with
default_features = false. (#286) -
breaking:
Route::boxedandBoxRoutehave been removed as they're no longer necessary (#404) -
breaking:
Nested,Ortypes are now private. They no longer had to be public becauseRouteris internally boxed (#404) -
breaking: Remove
routing::Layeredas it didn't actually do anything and thus wasn't necessary -
breaking: Vendor
AddExtensionLayerandAddExtensionto reduce public dependencies -
breaking:
body::BoxBodyis now a type alias forhttp_body::combinators::UnsyncBoxBodyand thus is no longerSync. This is because bodies are streams and requiring streams to beSyncis unnecessary. -
added: Implement
IntoResponseforhttp_body::combinators::UnsyncBoxBody. -
added: Add
Handler::into_make_servicefor serving a handler without aRouter. -
added: Add
Handler::into_make_service_with_connect_infofor serving a handler without aRouter, and storing info about the incoming connection. -
breaking: axum's minimum supported rust version is now 1.54
-
- Routing:
- Big internal refactoring of routing leading to several improvements (#363)
- added: Wildcard routes like
.route("/api/users/*rest", service)are now supported. - fixed: The order routes are added in no longer matters.
- fixed: Adding a conflicting route will now cause a panic instead of silently making a route unreachable.
- fixed: Route matching is faster as number of routes increases.
- breaking: Handlers for multiple HTTP methods must be added in the same
Router::routecall. So.route("/", get(get_handler).post(post_handler))and not.route("/", get(get_handler)).route("/", post(post_handler)).
- added: Wildcard routes like
- fixed: Correctly handle trailing slashes in routes:
- If a route with a trailing slash exists and a request without a trailing slash is received, axum will send a 301 redirection to the route with the trailing slash.
- Or vice versa if a route without a trailing slash exists and a request with a trailing slash is received.
- This can be overridden by explicitly defining two routes: One with and one without a trailing slash.
- breaking: Method routing for handlers has been moved from
axum::handlertoaxum::routing. Soaxum::handler::getnow lives ataxum::routing::get(#405) - breaking: Method routing for services has been moved from
axum::servicetoaxum::routing::service_method_routing. Soaxum::service::getnow lives ataxum::routing::service_method_routing::get, etc. (#405) - breaking:
Router::orrenamed toRouter::mergeand will now panic on overlapping routes. It now only acceptsRouters and not generalServices. UseRouter::fallbackfor adding fallback routes (#408) - added:
Router::fallbackfor adding handlers for request that didn't match any routes.Router::fallbackmust be use instead ofnest("/", _)(#408) - breaking:
EmptyRouterhas been renamed toMethodNotAllowedas it's only used in method routers and not in path routers (Router) - breaking: Remove support for routing based on the
CONNECTmethod. An example of combining axum with and HTTP proxy can be found here (#428)
- Big internal refactoring of routing leading to several improvements (#363)
- Extractors:
- fixed: Expand accepted content types for JSON requests (#378)
- fixed: Support deserializing
i128andu128inextract::Path - breaking: Automatically do percent decoding in
extract::Path(#272) - breaking: Change
Connected::connect_infoto returnSelfand remove the associated typeConnectInfo(#396) - added: Add
extract::MatchedPathfor accessing path in router that matched the request (#412)
- Error handling:
-
breaking: Simplify error handling model (#402):
- All services part of the router are now required to be infallible.
- Error handling utilities have been moved to an
error_handlingmodule. Router::check_infalliblehas been removed since routers are always infallible with the error handling changes.- Error handling closures must now handle all errors and thus always return
something that implements
IntoResponse.
With these changes handling errors from fallible middleware is done like so:
use axum::{ routing::get, http::StatusCode, error_handling::HandleErrorLayer, response::IntoResponse, Router, BoxError, }; use tower::ServiceBuilder; use std::time::Duration; let middleware_stack = ServiceBuilder::new() // Handle errors from middleware // // This middleware most be added above any fallible // ones if you're using `ServiceBuilder`, due to how ordering works .layer(HandleErrorLayer::new(handle_error)) // Return an error after 30 seconds .timeout(Duration::from_secs(30)); let app = Router::new() .route("/", get(|| async { /* ... */ })) .layer(middleware_stack); fn handle_error(_error: BoxError) -> impl IntoResponse { StatusCode::REQUEST_TIMEOUT }And handling errors from fallible leaf services is done like so:
use axum::{ Router, service, body::Body, routing::service_method_routing::get, response::IntoResponse, http::{Request, Response}, error_handling::HandleErrorExt, // for `.handle_error` }; use std::{io, convert::Infallible}; use tower::service_fn; let app = Router::new() .route( "/", get(service_fn(|_req: Request<Body>| async { let contents = tokio::fs::read_to_string("some_file").await?; Ok::<_, io::Error>(Response::new(Body::from(contents))) })) .handle_error(handle_io_error), ); fn handle_io_error(error: io::Error) -> impl IntoResponse { // ... }
-
- Misc:
0.2.8 (07. October, 2021)
- Document debugging handler type errors with "axum-debug" (#372)
0.2.7 (06. October, 2021)
- Bump minimum version of async-trait (#370)
0.2.6 (02. October, 2021)
- Clarify that
handler::anyandservice::anyonly accepts standard HTTP methods (#337) - Document how to customize error responses from extractors (#359)
0.2.5 (18. September, 2021)
0.2.4 (10. September, 2021)
- Document using
StreamExt::splitwithWebSocket(#291) - Document adding middleware to multiple groups of routes (#293)
0.2.3 (26. August, 2021)
- fixed: Fix accidental breaking change introduced by internal refactor.
BoxRouteused to beSyncbut was accidental made!Sync(#273)
0.2.2 (26. August, 2021)
- fixed: Fix URI captures matching empty segments. This means requests with
URI
/will no longer be matched by/:key(#264) - fixed: Remove needless trait bounds from
Router::boxed(#269)
0.2.1 (24. August, 2021)
- added: Add
Redirect::toconstructor (#255) - added: Document how to implement
IntoResponsefor custom error type (#258)
0.2.0 (23. August, 2021)
-
Overall:
-
Routing:
- added: Add dedicated
Routerto replace theRoutingDsltrait (#214) - added: Add
Router::orfor combining routes (#108) - fixed: Support matching different HTTP methods for the same route that aren't defined
together. So
Router::new().route("/", get(...)).route("/", post(...))now accepts bothGETandPOST. Previously onlyPOSTwould be accepted (#224) - fixed:
getroutes will now also be called forHEADrequests but will always have the response body removed (#129) - changed: Replace
axum::route(...)withaxum::Router::new().route(...). This means there is now only one way to create a new router. Same goes foraxum::routing::nest. (#215) - changed: Implement
routing::MethodFilterviabitflags(#158) - changed: Move
handle_errorfromServiceExttoservice::OnMethod(#160)
With these changes this app using 0.1:
use axum::{extract::Extension, prelude::*, routing::BoxRoute, AddExtensionLayer}; let app = route("/", get(|| async { "hi" })) .nest("/api", api_routes()) .layer(AddExtensionLayer::new(state)); fn api_routes() -> BoxRoute<Body> { route( "/users", post(|Extension(state): Extension<State>| async { "hi from nested" }), ) .boxed() }Becomes this in 0.2:
use axum::{ extract::Extension, handler::{get, post}, routing::BoxRoute, Router, }; let app = Router::new() .route("/", get(|| async { "hi" })) .nest("/api", api_routes()); fn api_routes() -> Router<BoxRoute> { Router::new() .route( "/users", post(|Extension(state): Extension<State>| async { "hi from nested" }), ) .boxed() } - added: Add dedicated
-
Extractors:
- added: Make
FromRequestdefault to being generic overbody::Body(#146) - added: Implement
std::error::Errorfor all rejections (#153) - added: Add
OriginalUrifor extracting original request URI in nested services (#197) - added: Implement
FromRequestforhttp::Extensions(#169) - added: Make
RequestParts::{new, try_into_request}public so extractors can be used outside axum (#194) - added: Implement
FromRequestforaxum::body::Body(#241) - changed: Removed
extract::UrlParamsandextract::UrlParamsMap. Useextract::Pathinstead (#154) - changed:
extractor_middlewarenow requiresRequestBody: Default(#167) - changed: Convert
RequestAlreadyExtractedto an enum with each possible error variant (#167) - changed:
extract::BodyStreamis no longer generic over the request body (#234) - changed:
extract::Bodyhas been renamed toextract::RawBodyto avoid conflicting withbody::Body(#233) - changed:
RequestPartschanges (#153)methodnew returns an&http::Methodmethod_mutnew returns an&mut http::Methodtake_methodhas been removedurinew returns an&http::Uriuri_mutnew returns an&mut http::Uritake_urihas been removed
- changed: Remove several rejection types that were no longer used (#153) (#154)
- added: Make
-
Responses:
- added: Add
Headersfor easily customizing headers on a response (#193) - added: Add
Redirectresponse (#192) - added: Add
body::StreamBodyfor easily responding with a stream of byte chunks (#237) - changed: Add associated
BodyandBodyErrortypes toIntoResponse. This is required for returning responses with bodies other thanhyper::Bodyfrom handlers. See the docs for advice on how to implementIntoResponse(#86) - changed:
tower::util::Eitherno longer implementsIntoResponse(#229)
This
IntoResponsefrom 0.1:use axum::{http::Response, prelude::*, response::IntoResponse}; struct MyResponse; impl IntoResponse for MyResponse { fn into_response(self) -> Response<Body> { Response::new(Body::empty()) } }Becomes this in 0.2:
use axum::{body::Body, http::Response, response::IntoResponse}; struct MyResponse; impl IntoResponse for MyResponse { type Body = Body; type BodyError = <Self::Body as axum::body::HttpBody>::Error; fn into_response(self) -> Response<Self::Body> { Response::new(Body::empty()) } } - added: Add
-
SSE:
- added: Add
response::sse::Sse. This implements SSE using a response rather than a service (#98) - changed: Remove
axum::sse. It has been replaced byaxum::response::sse(#98)
Handler using SSE in 0.1:
use axum::{ prelude::*, sse::{sse, Event}, }; use std::convert::Infallible; let app = route( "/", sse(|| async { let stream = futures::stream::iter(vec![Ok::<_, Infallible>( Event::default().data("hi there!"), )]); Ok::<_, Infallible>(stream) }), );Becomes this in 0.2:
use axum::{ handler::get, response::sse::{Event, Sse}, Router, }; use std::convert::Infallible; let app = Router::new().route( "/", get(|| async { let stream = futures::stream::iter(vec![Ok::<_, Infallible>( Event::default().data("hi there!"), )]); Sse::new(stream) }), ); - added: Add
-
WebSockets:
- changed: Change WebSocket API to use an extractor plus a response (#121)
- changed: Make WebSocket
Messagean enum (#116) - changed:
WebSocketnow usesErroras its error type (#150)
Handler using WebSockets in 0.1:
use axum::{ prelude::*, ws::{ws, WebSocket}, }; let app = route( "/", ws(|socket: WebSocket| async move { // do stuff with socket }), );Becomes this in 0.2:
use axum::{ extract::ws::{WebSocket, WebSocketUpgrade}, handler::get, Router, }; let app = Router::new().route( "/", get(|ws: WebSocketUpgrade| async move { ws.on_upgrade(|socket: WebSocket| async move { // do stuff with socket }) }), ); -
Misc
- added: Add default feature
tower-logwhich exposestower'slogfeature. (#218) - changed: Replace
body::BoxStdErrorwithaxum::Error, which supports downcasting (#150) - changed:
EmptyRouternow requires the response body to implementSend + Sync + 'static'(#108) - changed:
Router::check_infalliblenow returns aCheckInfallibleservice. This is to improve compile times (#198) - changed:
Router::into_make_servicenow returnsrouting::IntoMakeServicerather thantower::make::Shared(#229) - changed: All usage of
tower::BoxErrorhas been replaced withaxum::BoxError(#229) - changed: Several response future types have been moved into dedicated
futuremodules (#133) - changed:
EmptyRouter,ExtractorMiddleware,ExtractorMiddlewareLayer, andQueryStringMissingno longer implementCopy(#132) - changed:
service::OnMethod,handler::OnMethod, androuting::Nestedhave new response future types (#157)
- added: Add default feature
0.1.3 (06. August, 2021)
- Fix stripping prefix when nesting services at
/(#91) - Add support for WebSocket protocol negotiation (#83)
- Use
pin-project-liteinstead ofpin-project(#95) - Re-export
httpcrate andhyper::Server(#110) - Fix
QueryandFormextractors giving bad request error when query string is empty. (#117) - Add
Pathextractor. (#124) - Fixed the implementation of
IntoResponseof(HeaderMap, T)and(StatusCode, HeaderMap, T)would ignore headers fromT(#137) - Deprecate
extract::UrlParamsandextract::UrlParamsMap. Useextract::Pathinstead (#138)
0.1.2 (01. August, 2021)
- Implement
StreamforWebSocket(#52) - Implement
SinkforWebSocket(#52) - Implement
Derefmost extractors (#56) - Return
405 Method Not Allowedfor unsupported method for route (#63) - Add extractor for remote connection info (#55)
- Improve error message of
MissingExtensionrejections (#72) - Improve documentation for routing (#71)
- Clarify required response body type when routing to
tower::Services (#69) - Add
axum::body::box_bodyto converting anhttp_body::Bodytoaxum::body::BoxBody(#69) - Add
axum::ssefor Server-Sent Events (#75) - Mention required dependencies in docs (#77)
- Fix WebSockets failing on Firefox (#76)
0.1.1 (30. July, 2021)
- Misc readme fixes.
0.1.0 (30. July, 2021)
- Initial release.