如何检测访问者是否正在使用HTTP/2或SPDY-HowtodetectifthevisitorisusingHTTP/2orSPDY

4  

Theoretically, once nextHopProtocol lands in ResourceTiming and NavigationTiming, you should be able to detect h2 support for the root page and other resources.

从理论上讲，一旦nextHopProtocol登陆ResourceTiming和NavigationTiming，您应该能够检测到对根页面和其他资源的h2支持。

As of 2016-06-06, nextHopProtocol is only available in Firefox's ResourceTiming implementation. It is not available in their NavigationTiming, or in either NavigationTiming nor ResourceTiming for Chrome, FF, and Safari.

截至2016-06-06，nextHopProtocol仅适用于Firefox的ResourceTiming实现。它不适用于NavigationTiming，也不适用于Chrome，FF和Safari的NavigationTiming和ResourceTiming。

So for Firefox visitors today, you could see if nextHopProtocol is h2 for other resources on the same domain as the HTML page, and infer that the HTML page is h2 as well.

因此，对于今天的Firefox访问者，您可以看到nextHopProtocol对于与HTML页面位于同一域的其他资源是否为h2，并推断HTML页面也是h2。

0  

I didn't find a straightforward test. i think a workaround would be to write your own test :) You can get a list of browsers that support HTTP/2 (can be found on caniuse.com) then loop through the list of supporting browsers, if the current browser serving you is in the list then you are good to go.

我没有找到一个简单的测试。我认为解决方法是编写自己的测试:)你可以获得支持HTTP / 2的浏览器列表（可以在caniuse.com上找到）然后循环浏览支持的浏览器列表，如果当前的浏览器为你服务的话在列表中，你很高兴。

0  

It is July, 2018 and I see both Firefox and Chrome exposing this through Navigation Timing 2 API:

它是2018年7月，我看到Firefox和Chrome都通过Navigation Timing 2 API公开了这个：

performance.getEntriesByType('navigation')[0].nextHopProtocol

That being said, Navigation Timing Level 2 API is currently in working draft status so support for the nextHopProtocol (which is being introduced with Level 2 API) will be limited (unsure of exact browsers supporting it since caniuse currently doesn't include Navigation Timing Level 2 API).

话虽如此，导航时间等级2 API目前处于工作草案状态，因此对nextHopProtocol（正在使用Level 2 API引入）的支持将受到限制（不确定支持它的确切浏览器，因为caniuse目前不包括导航时间等级2 API）。