chore(deps): update rust crate tower-http to v0.7.1 #200
No reviewers
Labels
No labels
kind
bug
kind
enhancement
wayfinder
grilling
wayfinder
map
wayfinder
prototype
wayfinder
research
wayfinder
task
workflow
needs-info
workflow
needs-triage
workflow
ready-for-agent
workflow
ready-for-human
workflow
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
rosa/vernier!200
Loading…
Reference in a new issue
No description provided.
Delete branch "renovate/tower-http-0.x-lockfile"
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.7.0→0.7.1Release Notes
tower-rs/tower-http (tower-http)
v0.7.1Compare Source
Added
fs: addServeDir::redirect_to_trailing_slash()to serve directory indexes directly instead of first redirecting to the trailing-slash path. The redirect remains the default (#728)fs: addignore_multi_range_requests()toServeDirandServeFile, serving the full representation when a request asks for multiple byte ranges. The existing416 Range Not Satisfiableresponse remains the default (#727)request-id: the constructors and accessors on the request-id layers, services, andRequestIdare nowconst fn, so they can be used in const context (#716)Changed
fs: the minimumhttp-range-headerrequirement is now 0.4.2 (#661)Fixed
fs: makeServeDir::try_callpropagate expected filesystemI/O errors when no fallback is configured, as documented, instead of converting
them to
404 Not Foundresponses (#718)decompression: don't end the body when a data frame with no remaining bytesarrives after the decompressor reports end-of-stream. Trailers following such a
frame were dropped and could not be recovered (#722)
decompression: return a body error when a data frame with remaining bytesarrives after the decompressor reports end-of-stream, rather than silently
truncating. This regressed in 0.7.0 (#712)
fs: multipart range requests are now rejected before range validation, sothey consistently return
416 Range Not Satisfiablewith aCannot serve multipart range requestsbody instead of a genericunsatisfiable-range response (#661)
fs: range error responses no longer carry representation headers such asContent-TypeandContent-Encoding(#727)set-header:SetMultipleResponseHeadersLayerandSetMultipleResponseHeaderare now
Cloneregardless of the response body type, matching the fix appliedto the request-side types in 0.7.0 (#714)
All the changes
New Contributors
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate.
Branch automerge failure
This PR was configured for branch automerge. However, this is not possible, so it has been raised as a PR instead.
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.