Update Rust crate axum to 0.5.17 - autoclosed #5
Reference in New Issue
Block a user
No description provided.
Delete Branch "renovate/axum-0.x"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
0.5.13->0.5.170.5.1->0.5.17Release Notes
tokio-rs/axum
v0.5.17Compare Source
#[track_caller]so the errormessage points to where the user added the invalid router, rather than
somewhere internally in axum (#1248)
Multipartextractor work withRequestBodyLimitmiddleware (#1379)DefaultBodyLimit::maxfor changing the default body limit (#1397)v0.5.16Compare Source
Security
breaking: Added default limit to how much data
Bytes::from_requestwillconsume. Previously it would attempt to consume the entire request body
without checking its length. This meant if a malicious peer sent an large (or
infinite) request body your server might run out of memory and crash.
The default limit is at 2 MB and can be disabled by adding the new
DefaultBodyLimit::disable()middleware. See its documentation for moredetails.
This also applies to these extractors which used
Bytes::from_requestinternally:
FormJsonStringThanks to Shachar Menashe for reporting this vulnerability.
(#1346)
v0.5.15Compare Source
Note: This is a re-release of 0.5.14 that fixes an accidental breaking change.
QueryRejectionresponse. (#1171)v0.5.14Compare Source
Yanked, as it contained an accidental breaking change.
Configuration
📅 Schedule: At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR has been generated by Renovate Bot.
Update Rust crate axum to 0.5.17to Update Rust crate axum to 0.5.17 - autoclosedPull request closed