W3C home > Mailing lists > Public > public-web-perf@w3.org > April 2013

Re: [Resource Timing] Why does connectEnd exclude the SSL Handshake?

From: Austin,Daniel <daaustin@paypal-inc.com>
Date: Wed, 10 Apr 2013 14:45:18 +0000
To: James Simonsen <simonjam@google.com>
CC: Andy Davies <dajdavies@gmail.com>, "public-web-perf@w3.org" <public-web-perf@w3.org>
Message-ID: <380D0FF6-71E5-4B7B-910E-F512A077EA76@paypal.com>
There is no such animal as 'SecureConnectionEnd', in either nav or res timing. It's a significant flaw in the model. Also missing are details about the underlying OCSP calls. This significantly reduces the utility of the spec, IMHO.


Sent from my iPhone

On Apr 10, 2013, at 3:56 AM, "James Simonsen" <simonjam@google.com<mailto:simonjam@google.com>> wrote:

I can only guess it's because that's covered by sslConnectStart/End. But in the case of browsers that don't provide that, it seems like they should fall back to including it connectStart/End. Anyone else have an opinion?


On Tue, Apr 9, 2013 at 12:16 PM, Andy Davies <dajdavies@gmail.com<mailto:dajdavies@gmail.com>> wrote:
I understand why the spec states that connectEnd excludes SOCKS authentication etc., but don't quite understand why it excludes the SSL Handshake

"connectEnd must include the time interval to establish the transport connection. It must not include other time interval such as SSL handshake and SOCKS authentication."

I've had a hunt back through the archives but I couldn't find any reference as to why.

Is anyone able to explain?


Received on Wednesday, 10 April 2013 14:45:48 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:04:35 UTC