On Apr 17, 2009, at 7:45 PM, Amos Jeffries wrote:
Chris Woodfield wrote:
Hi,
We've noticed that when a request is sent that has multiple byte
ranges in the Range: header, the behavior is not what one would
expect.
If one requests multiple byte ranges that are sequential and do not
overlap
Chris Woodfield wrote:
Hi,
We've noticed that when a request is sent that has multiple byte ranges
in the Range: header, the behavior is not what one would expect.
If one requests multiple byte ranges that are sequential and do not
overlap (i.e. Range: bytes=1-20,30-50), the response is the
Hi,
We've noticed that when a request is sent that has multiple byte
ranges in the Range: header, the behavior is not what one would expect.
If one requests multiple byte ranges that are sequential and do not
overlap (i.e. Range: bytes=1-20,30-50), the response is the expected
206 Partial
