1144627 - Devtools do not indicate a file was pushed from the server via HTTP2

Status: RESOLVED DUPLICATE of bug 1592529

(DevTools :: Netmonitor, defect)

Description

[Gregory Gross]

Attachment: http2_push_timing.png

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:36.0) Gecko/20100101 Firefox/36.0
Build ID: 20150224134236

Steps to reproduce:

1. Start nghttp:

nghttpd 8443 server.key cert.pem -p/index.html=/jquery.js

(or use the test server set up by Shawn Bissell for bug 1127618: https://54.169.190.11:8443/ )

2. Turn off e10s (push doesn't work with e10s enabled, see 1127618).
3. Hit https://localhost:8443/index.html
4. Open devtools -> network tab
5. Refresh


Actual results:

Devtools does not show that jquery.js was pushed.
It also does not show how long jquery.js took to download (like it would have if it was not pushed).
It also does not show the total time taken to load the page on the bottom right, it shows "0s" (as in zero seconds).


Expected results:

Devtools should indicate that jquery.js was sent via PUSH_PROMISE and should include timings like it does for all other requests.

It shold also display the total time taken to load the page in the bottom right.

Comment 1

[J. Ryan Stinnett [:jryans] (Use needinfo, replies may be slow)]

Attachment: Version field in Net Monitor

Do you see this "Version" field in the Headers tabs for the request?

Comment 2

[Gregory Gross]

The version is there, yes, but the version does not specify whether a request was pushed with a PUSH_PROMISE frame or a traditional client request. I'd like to see what requests were pushed from the server using PUSH_PROMISE specifically.

This would be useful for debugging performance issues - and understanding what effect PUSH_PROMISE has on perceived latency. Showing this information in the timeline would be particularly useful to compare the traditional request/response approach vs using PUSH_PROMISE.

Comment 3

[J. Ryan Stinnett [:jryans] (Use needinfo, replies may be slow)]

Okay, thanks for clarifying!

Comment 4

[:Harald Kirschner :digitarald]

Continued in bug 1592529 fo feature scoping.