New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.
Starred by 1 user

Issue metadata

Status: Started
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug

Sign in to add a comment

ResourceTiming encodedBodySize and decodedBodySize are 0 for 304 Not Modified responses

Reported by, Apr 17

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.181 Safari/537.36

Steps to reproduce the problem:
1. Initiate a conditional get for a resource that returns a 304 Not Modified
2. Examine the ResourceTiming entry for this resource

Example test case is at:
1. Load
2. Soft-refresh
3. See that the page reports the encodedBodySize and decodedBodySize attributes are 0

What is the expected behavior?
The encodedBodySize and decodedBodySize attributes should "... reports the size of the previously retrieved payload body" per the ResourceTiming2 spec:

What went wrong?
The encodedBodySize and decodedBodySize attributes are 0.

Did this work before? No 

Does this work in other browsers? Yes

Chrome version: 65.0.3325.181  Channel: stable
OS Version: 10.0
Flash Version:
Firefox 59 returns the encodedBodySize and decodedBodySize of the cached content.
Labels: Needs-Triage-M65
Labels: M-68 Triaged-ET FoundIn-68 Target-68
Status: Untriaged (was: Unconfirmed)
Able to reproduce this issue on reported version 65.0.3325.181, on latest stable 66.0.3359.117 and on latest canary 68.0.3398.0 using Windows 10, Ubuntu 14.04 and Mac 10.13.3

This issue is seen from M-60. Hence considering this issue as Non-Regression and marking as Untriaged.

Components: -Blink>PerformanceAPIs Blink>PerformanceAPIs>ResourceTiming
Status: Available (was: Untriaged)
Status: Assigned (was: Available)
Status: Started (was: Assigned)

Sign in to add a comment