On 26.09.2011 19:07, Jim Jagielski wrote: > > On Sep 26, 2011, at 12:58 PM, Stefan Fritsch wrote: > >> >> But we are breaking quite a few popular clients here: VLC, everything >> based on lavf, firefox (the ogg media support). >> >> And httpd violates a SHOULD with the current form of RFC 2616 14.35.1: >> >> If a syntactically valid byte-range-set includes at least one byte- >> range-spec whose first-byte-pos is less than the current length of >> the entity-body, or at least one suffix-byte-range-spec with a non- >> zero suffix-length, then the byte-range-set is satisfiable. >> Otherwise, the byte-range-set is unsatisfiable. >> >> This means "0-" is satisfiable. >> >> If the byte-range-set >> is unsatisfiable, the server SHOULD return a response with a status >> of 416 (Requested range not satisfiable). Otherwise, the server >> SHOULD return a response with a status of 206 (Partial Content) >> containing the satisfiable ranges of the entity-body. >> >> In this case, I am strongly in favor of fixing the RFC first and >> changing httpd's behaviour only after that. >> > > Certainly we can have a config option on whether to > be strict or loose about it… > > ie: > > strict: 0- returns 200 > loose: 0- returns 206 > > and we can have 2.0 and 2.2's default be loose and 2.4's > be strict.
+1 Rainer
