fix(request): accept single-byte ranges in parseRange

[shimonewman]

RFC 9110 byte-range bounds are inclusive, so bytes=0-0 (a one-byte range, commonly sent by Safari/iOS players probing range support) and a request for a file's final byte are valid. parseRange() rejected any range where start >= end, so these requests parsed as no-range and consumers answered 416. Only start > end is invalid.

[github-actions]

Thanks for contributing! This repository is a read-only mirror; development for this library happens in packages/http in the utopia-php monorepo. Please open this pull request there instead.

[greptile-apps]

Greptile Summary

Corrects Request::parseRange() to accept inclusive single-byte byte ranges where the start and end offsets are equal.

• Changes the invalid-range check from start >= end to start > end.
• Adds coverage for the first byte, a later single byte, and a reversed invalid range.

Confidence Score: 5/5

The pull request appears safe to merge with no actionable correctness or security issues identified.

The changed comparison correctly accepts equal inclusive bounds, retains rejection of start-greater-than-end ranges, and is covered by targeted regression tests.

Important Files Changed

Filename	Overview
src/Http/Request.php	Aligns range validation with inclusive RFC 9110 bounds while continuing to reject reversed intervals.
tests/RequestTest.php	Adds focused regression coverage for equal-bound single-byte ranges and preserves coverage for invalid reversed bounds.

_{Reviews (1): Last reviewed commit: "fix(request): accept single-byte ranges ..." | Re-trigger Greptile}