http-range-header

An http range header parsing library focusing on correctness

Latest version: 0.4.2 registry icon
Maintenance score
0
Safety score
0
Popularity score
3
Check your open source dependency risks. Get immediate insight about security, stability and licensing risks.
Security
  Vulnerabilities
Version Suggest Low Medium High Critical
0.4.2 0 0 0 0 0
0.4.1 0 0 0 0 0
0.4.0 0 0 0 0 0
0.3.1 0 0 0 0 0
0.3.0 0 0 0 0 0
0.2.2 0 0 0 0 0
0.2.1 0 0 0 0 0

Stability
Latest release:

0.4.2 - This version may not be safe as it has not been updated for a long time. Find out if your coding project uses this component and get notified of any reported security vulnerabilities with Meterian-X Open Source Security Platform

Licensing

Maintain your licence declarations and avoid unwanted licences to protect your IP the way you intended.

MIT   -   MIT License

Not a wildcard

Not proprietary

OSI Compliant



Range header parsing

Latest workflow CratesIo

The main goals of this parser is:

  • Follow specification RFC-2616
  • Behave as expected MDN
  • Accuracy - parses headers strictly
  • Security - Never panics, ensured by fuzzing
  • Stability
  • No dependecies

Secondary goals are:

  • Speed
  • Information on why the header was rejected

The parser is strict. Any range where all parts are not syntactically correct and makes sense in the context of the underlying resource will be rejected.

Dev release checklist

  1. Make sure CI passes
  2. Run cargo fuzz cargo +nightly fuzz run random_string_input, at least a minute should be good enough. If it doesn't error out it has passed.
  3. Check msrv with for example cargo msrv, if a higher msrv is wanted/needed, bump it so that it's less than or equal to tower-http's
  4. Update changelog
  5. Update version
  6. Publish