Just use 'HTTP/2' for HTTP/2 not 'h2'
Reported by
mike.mac...@gmail.com,
Jun 20 2017
|
||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Safari/537.36 Steps to reproduce the problem: 1. Open DevTools 2. Look at an HTTP/2 request in the Network Panel 3. Add 'Protocol' What is the expected behavior? See 'HTTP/2' as the Protocol What went wrong? See the protocol is 'h2'. Think maybe 'h2' is HTTP/2 but not be entirely sure. Google 'h2' then for some guys blog post. Learn about SPDY/3, H2-14, H2C-14 and other irrelevant stuff. Guess that 'h2' is probably HTTP/2 but wonder why it can't be just HTTP/2 like HTTP/1.1 is. Did this work before? N/A Chrome version: 58.0.3029.110 Channel: n/a OS Version: 10.0 Flash Version: Memegenerator is down, so please imagine the 'Cool guy Justin Timberlake in Social Network' image macro with: "Just use HTTP/2" "It's cleaner" Thanks spicy Chromepersons.
,
Jun 29 2017
,
Jun 29 2017
Looks to be a feature request ccing allada for more inputs on this. Thanks!
,
Jul 5 2017
HTTP/2 is a general term referring to the HTTP/2 protocol, but not specifying the transport layer. h2 referrs to HTTP/2 over TLS. h2c referrs to HTTP/2 over TCP. (see: https://http2.github.io/faq/#can-i-implement-http2-without-implementing-http11) Chrome only supports h2 for HTTP/2 at the moment. We choose to show h2 instead of HTTP/2 because we want users to know it's over a "secure" channel. Thanks for your feedback though! |
||||
►
Sign in to add a comment |
||||
Comment 1 by mike.mac...@gmail.com
, Jun 20 2017