[Webkit-unassigned] [Bug 171231] New: Resource Timing doesn't require Timing-Allow-Origin header for cross origin requests
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Mon Apr 24 10:26:18 PDT 2017
https://bugs.webkit.org/show_bug.cgi?id=171231
Bug ID: 171231
Summary: Resource Timing doesn't require Timing-Allow-Origin
header for cross origin requests
Product: WebKit
Version: Safari Technology Preview
Hardware: Macintosh
OS: macOS 10.12
Status: NEW
Severity: Normal
Priority: P2
Component: New Bugs
Assignee: webkit-unassigned at lists.webkit.org
Reporter: JFSIII at Gmail.com
According to https://w3c.github.io/resource-timing/#cross-origin-resources the following properties should be set to 0 for cross-origin requests:
redirectStart, redirectEnd, domainLookupStart, domainLookupEnd, connectStart, connectEnd, requestStart, responseStart, secureConnectionStart, transferSize, encodedBodySize, decodedBodySize
However, as shown in https://twitter.com/JFSIII/status/855505436971155456 & https://twitter.com/JFSIII/status/855531120800129024, this is not always the case.
--
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/20170424/cdc50f07/attachment.html>
More information about the webkit-unassigned
mailing list