W3C home > Mailing lists > Public > public-web-perf@w3.org > February 2012

Cross Origin and Resource Timing

From: Alois Reitbauer <alois.reitbauer@dynatrace.com>
Date: Wed, 15 Feb 2012 08:05:56 +0000
To: "public-web-perf@w3.org" <public-web-perf@w3.org>
Message-ID: <A8638EB8DF9DE24D8C1E12D326D97AC39998A3@ATEX01.dynatrace.local>
As far as I can remember the final decision was that for cross origin resources which do not have the allow origin header set no detailed timings but the total time to download the resources is shown. I checked again with the latest version of the spec and it says

, these attributes must be set to zero: redirectStart<http://w3c-test.org/webperf/specs/ResourceTiming/#redirect-start>, redirectEnd<http://w3c-test.org/webperf/specs/ResourceTiming/#redirect-end>, domainLookupStart<http://w3c-test.org/webperf/specs/ResourceTiming/#domainlookup-start>, domainLookupEnd<http://w3c-test.org/webperf/specs/ResourceTiming/#domainlookup-end>, connectStart<http://w3c-test.org/webperf/specs/ResourceTiming/#connect-start>, connectEnd<http://w3c-test.org/webperf/specs/ResourceTiming/#connect-end>, requestStart<http://w3c-test.org/webperf/specs/ResourceTiming/#request-start>, responseStart<http://w3c-test.org/webperf/specs/ResourceTiming/#response-start>, and responseEnd<http://w3c-test.org/webperf/specs/ResourceTiming/#response-end>.

This would mean that one only gets the fetchStart time which means that we only know when the download started but not when it is finished.

Did I miss anything here?

// Alois
Received on Wednesday, 15 February 2012 08:20:46 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 15 February 2012 08:20:46 GMT