NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
crates.io
crates.io, #798 most downloaded on crates.io
No-dep range header parser
Latest stable
1.0.0
Last release 16 days ago
06 Nov 2026
Ships fairly regularly
a new release about every 1.2 years
Nearly every release is documented
notes for 7 of 7 stable releases
1 version withdrawn
withdrawn after publishing
5 years old
8 releases · first in 2021
Drag across the ruler to compare, or tap a release to open it.
A lot of changes to match , that mainly means relaxing strictness. This has led to a performance increase of on average around ~25% on the benchmarks.
A lot of changes to match https://www.rfc-editor.org/rfc/rfc9110.html, that mainly means relaxing strictness. This has led to a performance increase of on average around ~25% on the benchmarks.
More valid expressions will now produce ranges. Unsatisfiable ranges will no longer cause an error if there are also satisfiable ranges. Generally, the rule is: If there is at least one satisfiable, valid range and no invalid ones it's not an error . Satisfiable ranges are filtered if they cannot properly index the file at the given validation length (Only applies to an empty file).
Hides the internal ranges so that assumptions about validity can't be invalidated but offers functions to view/take internals.
parse_range_header_with_max_ranges that accepts a configurable number of ranges, for when 100 just isn't enough.ParsedRanges::len] which gives the number of rangesParsedRanges::into_ranges] which destroys the struct, yielding the ranges https://github.com/MarcusGrass/http-range-header/issues/9parse_range_header("bytes=-1").unwrap().validate(0) == Ok(vec![]), before it
returned Err(FileSuffixOutOfBounds).parse_range_header with bytes=-0 will now succeed, but validate will fail instead.RangeUnsatisfiableError::Invalid when a range is rejected because it doesn't make senseRangeUnsatisfiableError::Rejected when a range is rejected because of tolerance (too many ranges, overlapping, empty ranges, etc.)RangeUnsatisfiableError::Unsatisfiable when a range is syntactically valid but cannot be satisfied against a given file sizeparse_range_header will by default reject more than 100 ranges in a single input.parse_range_header instead of validateSyntacticallyCorrectRange is now an enum, StartPosition and Endposition are deleted (merged into enum cases).bytes=-N with N larger than the file size) now selects the whole file instead
of being unsatisfiable, as specified by RFC 9110 14.1.2.Bytes=0-10bytes=00-10bytes=00-10 , 15-20bytes=0-1 ,, , 3-4 and produces the ranges 0..=1 and 3..=4Your coding agent can read these notes before it upgrades. Set up the MCP server →
Relax internals visibility
Relax internals visibility
Relaxes visibility of internals to help some use-cases, see https://github.com/MarcusGrass/http-range-header/issues/9
Fixed validation on files smaller than range
Fixed validation on files smaller than range
See changelog for 0.4.1, fixes panics when range is larger than file allows
Improve performance and CI
Improve performance and CI
Rust version features to improve performancewith_error_causeFix spec compliance, clean up
Fix spec compliance, clean up
Only use one error type
Only use one error type
Fix rejecting a single reversed range
Fix rejecting a single reversed range
### Added - Make some optimizations
One column per quarter.