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

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

From: James Simonsen <simonjam@google.com>
Date: Tue, 9 Apr 2013 13:22:57 -0700
Message-ID: <CAPVJQi=O4okEt3LvWL10-65SFucO0S+YxfJi1v4BpFTAgWAJ5w@mail.gmail.com>
To: Andy Davies <dajdavies@gmail.com>
Cc: "public-web-perf@w3.org" <public-web-perf@w3.org>
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> 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?
> Thanks
> Andy
Received on Wednesday, 10 April 2013 10:55:39 UTC

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