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

Issue 771167 link

Starred by 5 users

Issue metadata

Status: Duplicate
Merged: issue 763700
Owner:
Last visit > 30 days ago
Closed: Oct 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 1
Type: Bug



Sign in to add a comment

DevTools doesn’t show correct GZIP’d size of resources

Project Member Reported by surma@chromium.org, Oct 3 2017

Issue description

Chrome Version       : 63.0.3231.0
OS Version: OS X 10.12.6

What steps will reproduce the problem?
1. Open DevTools Network Panel with large request rows
2. Open a site that serves GZIP content (example: http://dassur.ma/things/dom2texture/). Ideally a site that serves a Content-Length header
3. Determine actual size of numbers over the wire (e.g. curl -H 'Accept-Encoding: gzip' <url> | wc -c)

What is the expected result?
The grey resource size should match the actual number of bytes transferred.


What happens instead of that?
Neither of the sizes match the actual number of bytes transferred.

For the example site above, DevTools shows 48.8KB and 48.4KB (grey). The actual number of bytes transferred is 10787.

 
Components: -Platform>DevTools Platform>DevTools>Network
Owner: allada@chromium.org
Status: Assigned (was: Unconfirmed)
I can reproduce this.

    curl -H 'Accept-Encoding: gzip' http://dassur.ma/things/dom2texture/ | wc -c

This reports 10793 but in DevTools, both values are ~49KB.
Note that http://dassur.ma/things/dom2texture/ doesn’t have a `Content-Length` header, but this shouldn’t affect the result.

There is a related bug where if the `Content-Length` header is incorrect (e.g. `Content-Length: 42` while the actual response size is `9001` bytes), DevTools reports the `Content-Length` header value as the size.

Comment 3 by surma@chromium.org, Oct 4 2017

Re #2: I tested it with a server that serves a correct `Content-Length` header and the bug persists.
Cc: clamy@chromium.org
Looks like it's from plzNavigate. I'll look deeper into it.

Comment 5 by clamy@chromium.org, Oct 16 2017

Cc: dgozman@chromium.org arthurso...@chromium.org
Yes that's likely. We've been encountering issues in the past with the proper transfer of the encoded data size of the navigation request to the renderer (where it will be displayed in DevTools).
Cc: caseq@chromium.org
This issue is also present in Chrome Version 61.0.3163.100 (OS X).

Comment 8 by addyo@chromium.org, Oct 17 2017

Cc: addyo@chromium.org
 Issue 775540  has been merged into this issue.
Components: UI>Browser>Navigation
Labels: -Pri-3 proj- Pri-1
This is becoming a significant issue. Can someone from PlzNavigate help diagnose what's happening here?
Mergedinto: 763700
Status: Duplicate (was: Assigned)
This has the same root cause as  issue 763700 .

Sign in to add a comment