W3C home > Mailing lists > Public > public-webappsec@w3.org > January 2014

[cors] Add 'Range' to simple headers

From: Steven Robertson <strobe@google.com>
Date: Mon, 13 Jan 2014 11:52:29 -0800
Message-ID: <CAJtuSCvXr09PN_938P6JWAY2xVn7S815Tg0DJt0ysyUzX6kCCA@mail.gmail.com>
To: public-webappsec@w3.org
Hello WebAppSec members,

The application I work on is latency-sensitive and uses the Media Source
API in concert with XHR to download media bytes. In order to avoid the
latency cost of a preflight to each host in our CDN, we have developed a
workaround where we use a 'range=' query arg to subset an existing
resource. This workaround is suboptimal, and we would prefer to use a Range
header, but the latency impact of the extra request has a significant
impact on quality of experience.

What are your thoughts regarding the addition of 'Range' as a simple
request header to allow for this use-case?

Thanks for your consideration!
Received on Monday, 13 January 2014 19:53:36 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:54:37 UTC