- From: Ilya Grigorik <igrigorik@google.com>
- Date: Wed, 12 Apr 2017 14:17:15 -0700
- To: Spencer Fricke <sjfricke@wisc.edu>
- Cc: "public-web-perf@w3.org" <public-web-perf@w3.org>
- Message-ID: <CADXXVKqNhGNNHLY8pd94Bk=ef1wVNArDvkeYzG_ap9fo2A86UQ@mail.gmail.com>
Hi Spencer. HAR spec is not something we maintain in this group.. AFAIK, the "official" version is at: http://www.softwareishard.com/blog/har-12-spec/ ig On Fri, Apr 7, 2017 at 7:07 PM, Spencer Fricke <sjfricke@wisc.edu> wrote: > So I noticed that the 1.2 HAR spec labels the "timing" field in the > *Entries* section as: > > > *time [number] - Total elapsed time of the request in milliseconds. This > is the sum of all timings available in the timings object (i.e. not > including -1 * > *values) . * > > This is misleading and incorrect as I have attached my example where I get > these values > > - "time": 322.7780000306666 > - "timings": { > "blocked": 0, > "dns": 0, > "connect": 170.783000008669, > "send": 0.5499999970199951, > "wait": 146.941000013612, > "receive": 4.5040000113655765, > "ssl": 137.33599998522573 > }, > > > As you can quick calculate the timings values are greater then 322 > > I have assumed that the *ssl *value is not part of the "time" as it is a > subset of the connect time. I purpose to change the wording of the "time" > spec from "*This is the sum of all timings available in the timings > object" to "**This is the sum of all timings available in the timings > object with the exception of the *ssl* field"* > > Thanks, > Spencer Fricke > >
Received on Wednesday, 12 April 2017 21:18:30 UTC