Bug 273295
| Summary: | decodedBodySize, encodedBodySize and transferSize are not populated with Timing-Allow-Origin * | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | alehm |
| Component: | Page Loading | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED WONTFIX | ||
| Severity: | Normal | CC: | achristensen, beidson, cdumez, webkit-bug-importer |
| Priority: | P2 | Keywords: | InRadar |
| Version: | Safari 17 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
alehm
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.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Radar WebKit Bug Importer
<rdar://problem/127466015>
Alex Christensen
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
alehm
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).