- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Thu, 09 Oct 2008 17:03:44 +0200
- To: Henrik Nordstrom <henrik@henriknordstrom.net>
- CC: "A. Rothman" <amichai2@amichais.bounceme.net>, ietf-http-wg@w3.org
Henrik Nordstrom wrote: > Obviously 2 is the correct answer. > > > responding with multipart/byteranges is only OK if the client issued a > request with multiple ranges, as this is how the client indicates it > supports multipart/byteranges. > > It's entirely fine to respond with a single range within that > multipart/byteranges response if the ranges adds up to a single range or > if the server otherwise chooses to respond with a single range. > > The MUST NOT is to respond with multipart/byteranges if the request was > for only one range as there is no way to know if the client supports > multipart/byteranges in response to such requests. > > As soon as the request is multi-ranged the server is free to choose > multipart/byteranges if it likes as it then knows the client supports > this, even if not strictly needed for the specific response. > > Responding with multipart/byteranges when there is only a single range > in the response is sub-optimal, but does not make it an invalid response > to a multi-range request. > > Regards > Henrik Ok, proposed change in <http://trac.tools.ietf.org/wg/httpbis/trac/attachment/ticket/133/133.diff>... BR, Julian
Received on Thursday, 9 October 2008 15:04:28 UTC