On 8/31/2011 4:00 PM, Stefan Fritsch wrote: > On Wednesday 31 August 2011, Joe Orton wrote: >> >> Anything else to watch out for? > > c) a request with a byterange beyond the end of the file used to > return 416 but now returns 200. This is a violation of a RFC2616 > SHOULD. We didn't catch this when testing. > This is how mplayer seems to determine that it has reached the end of > file. This seems a rather stupid thing to do unless mplayer assumes > that the file may grow. But as it's a SHOULD, we should fix it.
Yup, that's a major flaw. If one range may be satisfied, we may not return 416, but must return those ranges which we are able. If no ranges are satisfiable, the answer needs to be restored to 416.
