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

Issue 647255 link

Starred by 3 users

Issue metadata

Status: Fixed
Owner:
Last visit > 30 days ago
Closed: Nov 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 3
Type: Bug



Sign in to add a comment

Keep Alive missing from Connection column in Network Tools but shown in Request Headers

Reported by spen...@streetlike.com, Sep 15 2016

Issue description

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

Steps to reproduce the problem:
1. Opem Developer Tools->Network Tab
2. Go to www.sweatybetty.com
3. Show connection column
4. See that Keep-Alive missing from many rows
5. In Request headers though keep alive is there. See my screenshots for example of asset where this applies

What is the expected behavior?
That Keep Alive in connection column should match the Request Header

What went wrong?
Keep Alive is missing from Connection Column

Did this work before? N/A 

Chrome version: 53.0.2785.113  Channel: n/a
OS Version: 6.3
Flash Version: Shockwave Flash 23.0 r0
 
Connection - Keep Alive missing.JPG
110 KB View Download
Connection Keep Alive in Request Header.JPG
213 KB View Download
Components: -Platform>DevTools Platform>DevTools>Network
Labels: -OS-Windows OS-All
Owner: allada@chromium.org
Status: Assigned (was: Unconfirmed)

Comment 2 by allada@chromium.org, Sep 15 2016

Cc: paulir...@chromium.org
Labels: -Pri-2 Pri-3
I spoke to +paulirish about this and we came to an agreement on this as follows:

1) Network panel has some stuff heading down the pipeline that will help with displaying persistence/recycling of connections.
2) "Keep-Alive" is only useful for HTTP1/1.1 because h2/quic pretty much always uses the same connection.

Because of these we agreed that this is a problem, but investing into something that will only be usable for HTTP1/1.1 is probably not a good idea.

In a nutshell we are saying "Hold tight, we should have some stuff to help with your use case coming."

In the short term you can use the ConnectionId Column to help with this kind of issue.

[This is happening because 304 is implied Connection: keep-alive, but we only show it if it exists]

Comment 3 by allada@chromium.org, Nov 15 2016

Status: Fixed (was: Assigned)
This should now be addressed by setting a custom column in network panel.

Sign in to add a comment