Bug 193902 - [Resource Timing] Should surface entries for failed requests (DNS, TCP, SSL, 4xx, 5xx)
Summary: [Resource Timing] Should surface entries for failed requests (DNS, TCP, SSL, ...
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebCore Misc. (show other bugs)
Version: Safari 12
Hardware: All All
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-01-28 04:36 PST by Nic Jansma
Modified: 2019-01-28 04:36 PST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Nic Jansma 2019-01-28 04:36:37 PST
This is a request for an un-do of https://bugs.webkit.org/show_bug.cgi?id=104762

Per the latest ResourceTiming (Level 2) spec:

https://www.w3.org/TR/resource-timing-2/#resources-included-in-the-performanceresourcetiming-interface

> If a resource fetch was aborted due to a networking error (e.g. DNS, TCP, or TLS error), then the fetch MAY be included as a PerformanceResourceTiming object in the Performance Timeline with initialized attribute values up to the point of failure - e.g. a TCP handshake error should report DNS timestamps for the request, and so on.

While the language says MAY, I'm requesting that failed entries (transport-level and HTTP 4xx/5xx) be included in ResourceTiming in Safari.