- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Mon, 04 Jan 2010 13:26:49 +0100
- To: Philip Jägenstedt <philipj@opera.com>
- CC: "Tab Atkins Jr." <jackalmage@gmail.com>, Silvia Pfeiffer <silviapfeiffer1@gmail.com>, Anne van Kesteren <annevk@opera.com>, Edward O'Connor <hober0@gmail.com>, Jeremy Keith <jeremy@adactio.com>, HTMLwg <public-html@w3.org>
Philip Jägenstedt wrote: > ... > Why is that not good, and how could the browser possibly know that the > resource is not seekable without trying to GET it? > ... Unless I'm missing something, aborting the connection will not cause the server to stop sending immediately, so both network bandwidth and server resources are wasted. Furthermore, dropping the connection means you need to establish a new one, no? To find out about range request support, the client could do a HEAD request and check the Accept-Ranges response header (and yes, it's not required to return it, so it would be interesting to check what current servers do). > ... BR, Julian
Received on Monday, 4 January 2010 12:27:26 UTC