Re: #311: Denial of Service and Ranges

On Thu, Nov 24, 2011 at 5:24 PM, Mark Nottingham <> wrote:
> Roy raised the following about p5:
> 3) Clients that send Range requests containing multiple byterange specifiers MUST list those ranges in ascending order within the Range header field value. Servers MAY reorder multiple ranges if they are not requested in ascending order, or respond with a 416 or 200 status instead.

Out of order requests are very useful for readv style VFS calls, when
backed onto HTTP. Surely permitting out of order ranges is better than
having the clients pipeline them instead (with all the additional
overhead of separate requests).


Received on Thursday, 24 November 2011 04:56:54 UTC