W3C home > Mailing lists > Public > ietf-http-wg@w3.org > April to June 2010

Re: clarity needed for browser behaviors when receiving 206 status codes

From: Bjoern Hoehrmann <derhoermi@gmx.net>
Date: Fri, 25 Jun 2010 05:47:33 +0200
To: Marques Johansson <marques@displague.com>
Cc: ietf-http-wg@w3.org
Message-ID: <pl7826tm60268vca0da835krohk38ckinr@hive.bjoern.hoehrmann.de>
* Marques Johansson wrote:
>The HTTP specification for ranges does not deal with a few range
>related matters that I encountered while attempting to create a
>streaming video script.
>
>How can servers inform clients that all requests must be made with
>ranges specified?

As far as byte ranges are concerned, if the server is willing to accept
a range request for the "whole" resource, then the server should not in-
sist on the client making a range request. If it is not then the server
would need to tell the client what ranges are available, but that seems
to be more a 300 Multiple Choices kind of situation.

>How should a client or server respond when the server is not willing
>to fulfill the entire range requested by the client?

That depends on why it is not willing and possibly what could sway the
server to satisfy the request. Payment Required, Service Unavailable,
Unauthorized, and so on. In doubt 403 Forbidden with an Accept-Ranges
header in the response and a suitable entity body would seem sensible;
that also goes for your first question.
-- 
Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de
Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de
25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/ 
Received on Friday, 25 June 2010 03:48:06 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 06:51:20 GMT