feat: add Range header to ensure Content-Length is returned in response headers #1263
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This pull request includes updates to the versioning in
Cargo.toml
and an enhancement to the HTTP backend implementation to improve response handling. The most important changes are outlined below:Version Updates in
Cargo.toml
:1.0.7
to1.0.8
to reflect the new release. (Cargo.toml
, Cargo.tomlL15-R15)dragonfly-client
and related crates) to version1.0.8
for consistency with the new release. (Cargo.toml
, Cargo.tomlL25-R31)HTTP Backend Enhancement:
Range
header (bytes=0-
) to HTTP requests in thedragonfly-client-backend
to ensure theContent-Length
is included in the response headers. This addresses scenarios where servers usingTransfer-Encoding: chunked
may omitContent-Length
inHEAD
requests. (dragonfly-client-backend/src/http.rs
, dragonfly-client-backend/src/http.rsR141-R147)Related Issue
Motivation and Context
Screenshots (if appropriate)