Hey Ramsey,

thanks for the great work. I used your range parser as base for a new PSR Handler & Middleware, that I will publish soon. With my tests, a found an issue in your parser.

Best regards,
Tim

Description

I got this ParseException "Unable to parse range: 210-250" if the header is "bytes=0-199, 210-250"

Steps to reproduce

Call your code with a Range header incl. multiple ranges separated by space: bytes=0-199, 210-250

Expected behavior

I would expect the same behavior as with this header bytes=0-199,210-250 (without space). The space is allowed in this context and should be trimmed/skipped in the parsing process.

Same docs:

• https://developer.mozilla.org/en-US/docs/Web/HTTP/Range_requests
• https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Range

Environment details

• version of this package: dev-main
• PHP version: 8.2.7
• OS: current macOS

What is your opinion of changing the behavior of parseRange to match the same behavior as array_slice instead of throwing NotSatisfiableExceptions?

Example 1:

parseRange('0-300', 0); // => Throws NotSatisfiableException
array_slice([], 0, 300); // => []

When the entity has a totalSize of 0 you have to know that fact before requesting the range to avoid throwing an error.

Example 2:

parseRange('2-5', 1); // => Throws NotSatisfiableException
array_slice([0], 2, 5); // => []

The current behavior certainly makes sense (why would you request a random out-of-range range?), but it seems like conforming to a known interface/behavior like array_slice has some value.

Hi

Would it be possible for you to upgrade your package to use psr/http-message: ^2.0?

Any chance there could be a non-alpha release of this package?

Thanks!