You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When working with content ranges, all clients would need to perform the same content range parsing based on RFC. Would it be ok to add support for such parsing to the reqwest lib? I could try to provide a PR for that if there is interest.
Update I implemented this as a separate crate - not sure if the reqwest maintainers want to use it directly.
/// HTTP Content-Range response header representation.pubenumContentRange{/// Regular bytes range response with status 206Bytes(ContentRangeBytes),/// Regular bytes range response with status 206UnboundBytes(ContentRangeUnbound),/// Server response with status 416Unsatisfied(ContentRangeUnsatisfied),/// Header cannot be parsed. This includes non-standard response with status 206Unknown,}pubstructContentRangeBytes{pubfirst_byte:u64,publast_byte:u64,pubcomplete_length:u64,}pubstructContentRangeUnbound{pubfirst_byte:u64,publast_byte:u64,}pubstructContentRangeUnsatisfied{pubcomplete_length:u64,}
The text was updated successfully, but these errors were encountered:
When working with content ranges, all clients would need to perform the same content range parsing based on RFC. Would it be ok to add support for such parsing to the
reqwest
lib? I could try to provide a PR for that if there is interest.Update I implemented this as a separate crate - not sure if the reqwest maintainers want to use it directly.
The text was updated successfully, but these errors were encountered: