[Bug 4766] httpd fails to honor byte range requests if the range begins with 0

bugzilla at busybox.net bugzilla at busybox.net
Sat Feb 18 10:57:20 UTC 2012


--- Comment #3 from Bernhard Reutner-Fischer <aldot at uclibc.org> 2012-02-18 10:57:20 UTC ---
(In reply to comment #2)
> I don't know how sensitive BusyBox is to a word vs. a byte vs. a bit for data. 

You can check the size increase with
$ scripts/bloat-o-meter busybox_unstripped.unpatched busybox_unstripped
(cp busybox_unstripped busybox_unstripped.unpatched for a pristine build, then
apply your patch and rebuild).

> Negative values of range_start could also be used as a positive boolean,
> instead of the smallint range_req I've proposed.
> To summarize:
> if a range is requested and the Range: header is reasonable, set range_start to
> requested value | ~MAX_INT (sets high bit)
> range_start == 0 => no byte range requested or served
> range_start != 0 => serve a byte range starting from (range_start ^ ~MAX_INT)
> I don't know if BusyBox httpd has been tested or is expected to work with > 2GB
> files, though.

The httpd works fine with files > 2GB, yes.

Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

More information about the busybox-cvs mailing list