Description: ------------ The specification: http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.35.1 Stipulates: "If the last-byte-pos value is present, it MUST be greater than or equal to the first-byte-pos in that byte-range-spec, or the byte- range-spec is syntactically invalid. The recipient of a byte-range- set that includes one or more syntactically invalid byte-range-spec values MUST ignore the header field that includes that byte-range- set." The test of start <= end is not implemented in getChunks(). I'm preparing a patch.

After looking deeper in the code, it appears that last-byte >= first-byte is checked for, but at the wrong time (when some content range may have already be sent) and with the wrong behavior (returning 416, instead of ignoring the range request.) I'm still preparing a patch though :-)

The patches correct / enhance the package as follow: - Better detection of malformed Range header (bug #13124), - More compliant handling of malformed / unsatisfiable ranges (bug #13125), - Merges overlapping requested ranges, - Support for unknown content-length (for custom streams) (req #13121)

This bug has been fixed in SVN. If this was a documentation problem, the fix will appear on pear.php.net by the end of next Sunday (CET). If this was a problem with the pear.php.net website, the change should be live shortly. Otherwise, the fix will appear in the package's next release. Thank you for the report and for helping us make PEAR better.