har export does not generate http2 pseudo headers for :path and :authority for server push resources
Reported by
les.mur...@eperformancegroup.com,
Jan 2 2017
|
|||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.87 Safari/537.36 Steps to reproduce the problem: 1. Open Developer tools - Network Tab 2. Include column "Initiator" 3. load https://www.g2crowd.com/ or https://www.shimmercat.com/ or another h2 site that uses push 4. observe that resources were pushed by server 5. (optional) use net-internals to confirm that the push promise was made 6. Save as HAR with content What is the expected behavior? HAR file should have mandatory h2 pseudo headers for path and authority. What went wrong? The resource only has the Referer and User-Agent headers. The only way to determine the host of the resource would be to parse the request.url field. This extra step / workaround is not required for non-pushed resources. Did this work before? N/A Chrome version: 55.0.2883.87 Channel: stable OS Version: 10.0 Flash Version: Shockwave Flash 24.0 r0 A very nice to have would be some indicator that the resource was pushed.
,
Jan 3 2017
See also new bug I created - Issue 677862 . An overall review as to what should be included in a HAR for h2 resources would be helpful.
,
Jan 10 2017
,
Jul 20 2017
There was a recent refactor in this area. Most of this should be resolved. Please create a new bug if more HAR exporting errors are experienced. |
|||
►
Sign in to add a comment |
|||
Comment 1 by brajkumar@chromium.org
, Jan 2 2017