[Webkit-unassigned] [Bug 225733] New: Resource Timing: secureConnectionStart == 0 when a connection is re-used

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=225733

            Bug ID: 225733
           Summary: Resource Timing: secureConnectionStart == 0 when a
                    connection is re-used
           Product: WebKit
           Version: WebKit Nightly Build
          Hardware: Unspecified
                OS: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: Platform
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: nic at nicj.net

When a TLS connection is re-used, the secureConnectionStart attribute returns 0.

It should be set to the same as fetchStart, if a persistent connection is re-used, per:

https://www.w3.org/TR/resource-timing-1/#dom-performanceresourcetiming-secureconnectionstart

Example:

{
  "name": "[some re-used TLS connection URL]",
  "entryType": "resource",
  "startTime": 121,
  "duration": 0,
  "initiatorType": "link",
  "nextHopProtocol": "",
  "workerStart": 0,
  "redirectStart": 0,
  "redirectEnd": 0,
  "fetchStart": 121,
  "domainLookupStart": 121,
  "domainLookupEnd": 121,
  "connectStart": 121,
  "connectEnd": 121,
  "secureConnectionStart": 0,
  "requestStart": 121,
  "responseStart": 121,
  "responseEnd": 121
}

In the above example, secureConnectionStart should probably be 121 (the same as fetchStart, which is also what domainLookup* and connect* use).

This can also be seen in WPT test failures:

* https://wpt.fyi/results/resource-timing/resource_connection_reuse_mixed_content.html?label=experimental&label=master&aligned
* https://wpt.fyi/results/resource-timing?label=experimental&label=master&aligned

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20210513/72990f55/attachment-0001.htm>