Updates http-range-header to 0.4, it broke a test rejecting a spec-valid header so that's fixed here as well.
Added a bunch of tests in 0.4 re-ran the fuzzing and made a few optimizations. I think the performance increase was something like 15% across the board. Set the msrv on that project to the same as this one, 1.60.0. Added msrv to the package.metadata for tower-http, so I could run cargo msrv verify on it, it checks out.
Motivation
Fixes https://github.com/tower-rs/tower-http/issues/384
Solution
Updates http-range-header to
0.4, it broke a test rejecting a spec-valid header so that's fixed here as well. Added a bunch of tests in0.4re-ran the fuzzing and made a few optimizations. I think the performance increase was something like 15% across the board. Set the msrv on that project to the same as this one, 1.60.0. Added msrv to thepackage.metadatafortower-http, so I could runcargo msrv verifyon it, it checks out.The actual fix came from @jfaust in this PR https://github.com/MarcusGrass/http-range-header/pull/3