- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Mon, 08 Sep 2014 15:47:03 +0200
- To: Sandro Hawke <sandro@w3.org>, Amos Jeffries <squid3@treenet.co.nz>, ietf-http-wg@w3.org
On 2014-09-08 15:20, Sandro Hawke wrote: > ... > Can you point me to the part of a spec which says clients should treat > all unknown 2xx codes as if they were 200? I don't think that's how > unknown 2xx codes are supposed to be handled. > ... <http://svn.tools.ietf.org/svn/wg/httpbis/specs/rfc7231.html#rfc.section.6.p.2> > ... > It's possible we did this design before realizing Range could be used > with units other than bytes. Do you know of any deployments with > non-byte units? > > Is there a way to make Range work with changing resource state? What > happens if you have 100k units, and the client is reading 100 at a time, > and an item gets inserted or deleted near the beginning. It looks to > me like the client would miss a boundary item or see a duplicated item. > (We've addressed this in paging by varying the page size when that > happens.) This seems like it'd be outside of what the folks designing > Range were expecting, and so it wouldn't be properly handled. Hoping > I'm wrong.... > ... If-Range. See <http://svn.tools.ietf.org/svn/wg/httpbis/specs/rfc7233.html#rfc.section.3.2>. Best regards, Julian
Received on Monday, 8 September 2014 13:50:54 UTC