- From: Mark Watson <watsonm@netflix.com>
- Date: Wed, 16 May 2012 20:01:00 +0000
- To: "public-web-perf@w3.org" <public-web-perf@w3.org>
A simple way to handle the byte range issue would be to say that the name of the timing object for an HTTP request with a byte range header consists of the URL followed by a space followed by the byte range (in the same form as in the HTTP request, with any spaces removed). Spaces are not allowed in URLs, so this would be well-defined. …Mark
Received on Wednesday, 16 May 2012 20:01:30 UTC