Bug 273295 - decodedBodySize, encodedBodySize and transferSize are not populated with Timing-Allow-Origin *
Summary: decodedBodySize, encodedBodySize and transferSize are not populated with Timi...
Status: RESOLVED WONTFIX
Alias: None
Product: WebKit
Classification: Unclassified
Component: Page Loading (show other bugs)
Version: Safari 17
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords: InRadar
Depends on:
Blocks:
 
Reported: 2024-04-25 17:40 PDT by alehm
Modified: 2024-05-06 09:27 PDT (History)
4 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description alehm 2024-04-25 17:40:09 PDT
decodedBodySize, encodedBodySize and transferSize (tested only these) are not populated in PerformanceResourceTiming for cross origin requests with `Timing-Allow-Origin: *` http header set for both cached and non-cached resources. It works fine in Chrome and Firefox. See also https://w3c.github.io/resource-timing/#sec-cross-origin-resources.
Comment 1 Radar WebKit Bug Importer 2024-05-02 17:41:16 PDT
<rdar://problem/127466015>
Comment 2 Alex Christensen 2024-05-03 09:19:52 PDT
https://github.com/WebKit/WebKit/blob/main/Source/WebCore/page/PerformanceResourceTiming.cpp#L274

// This is intentionally stricter than a TAO check.
// See https://github.com/w3c/server-timing/issues/89
Comment 3 alehm 2024-05-06 09:27:12 PDT
Thank you for your response. Is there a plan to implement https://w3c.github.io/resource-timing/#dom-performanceresourcetiming-deliverytype? Otherwise, there is no way to find out whether a particular resource was loaded from the cache or not (without explicitly using Cache API or something similar).