Headless Chrome does not negotiate HTTP2
Reported by
yukiny...@gmail.com,
Jan 5 2017
|
||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.95 Safari/537.36 Example URL: Steps to reproduce the problem: 1. open headless chrome 2. go to http2.golang.org 3. open inspector 4. check protocol. It shows spdy What is the expected behavior? Protocol showing should be h2. What went wrong? It looks like headless chrome does not negotiate http2 correctly. Did this work before? N/A Chrome version: 57.0.2970.0 Channel: stable OS Version: Debian Jessie Flash Version: This issue and the screenshot are initially reported by Jan Šváger (https://twitter.com/svagis).
,
Jan 5 2017
I'm almost certain this is a devtools bug, as I don't think Chrome even still supports SPDY. When I flush sockets and cache, and open, say https://codereview.chromium.org/2613033003/ with devtools open, everything says H2. Reloading, everything still says H2, even things loaded from the memory cache. Opening the URL in a new tab (Keeping the old tab open as well), with dev tools open, in the new tab, resources loaded from the memory cache (Not the disk cache) all say they were downloaded via spdy, despite the fact that the original tab clearly says they were downloaded via h2.
,
Jan 5 2017
,
Jan 6 2017
Adding some recent CL authors touching https://cs.chromium.org/chromium/src/third_party/WebKit/Source/devtools/front_end/network/NetworkLogView.js, I think it's that part of the code. I cannot quite decipher where the protocol string is coming from.
,
Jan 10 2017
,
May 15 2017
,
Dec 1 2017
,
Jan 2 2018
Chrome 63.0.3239.108 reports "h2" for protocol in headless mode when visiting https://http2.golang.org, therefore I am closing this issue. I agree with comment #2 that Chrome is not supporting SPDY any longer, and it has not for a long time. |
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by yukiny...@gmail.com
, Jan 5 2017