为什么HTTP / 2上的特定网站在FF的作品，但在Chrome，IE和边缘相同的Windows 10的计算机上不起作用？ [英] Why HTTP/2 on a specific site works in FF, but doesn't work in Chrome, IE and Edge on the same Windows 10 computer?
问题描述
我有一个网站，那就在Ubuntu 16.04服务器（OpenSSL的1.0.2h）一个Nginx的1.10.0运行。我想为这个网站通过HTTP / 2，所以我配置了相应的Nginx：
I have a site, that runs on a Nginx 1.10.0 on Ubuntu 16.04 server (OpenSSL 1.0.2h). I want to serve this site over HTTP/2, so I configured Nginx accordingly:
listen 443 ssl http2 default_server;
listen [::]:443 ssl http2 default_server
和它在FF 47和Chrome 51在我的办公室的Ubuntu 15.10桌面和我家一样的浏览器的Ubuntu 15.10桌面。
And it works fine in FF 47 and Chrome 51 on my office Ubuntu 15.10 desktop and in the same browsers on my home Ubuntu 15.10 desktop.
不过在我家的Windows 10的台式机和笔记本电脑的HTTP / 2仅在FF。铬51，IE 11和边缘使用本网站HTTP / 1.1。
However on my home Windows 10 desktop and laptop HTTP/2 works only in FF. Chrome 51, IE 11 and Edge are using HTTP/1.1 on this site.
所以，我很困惑。 此服务说，我的网站支持HTTP / 2和ALPN（这是需要的HTTP / 2在Chrome中工作，因为版本51 ）。
So, I'm baffled. This service says, that my site supports HTTP/2 and ALPN (which is required for HTTP/2 to work in Chrome since version 51).
浏览器版本和功能是完全一样的：
Chrome versions and capabilities are exactly the same:
![Chrome的网络信息](\"http://i.stack.imgur.com/nBwx8.png\")
HTTPS的工作原理和安全小组在Chrome开发工具表明，这一切都是安全的。
HTTPS works, and Security panel in Chrome Dev Tools shows, that everything is secured.
在Chrome，IE和边缘此演示显示消息的此浏览器不是HTTP / 2启用。的和的您的浏览器支持HTTP / 2！的在FF。
但是，HTTP / 2 medium.com 在所有这一切的浏览器工作得很好。
This demo in Chrome, IE and Edge displays message "This browser is not HTTP/2 enabled.", and "Your browser supports HTTP/2!" in FF. But HTTP/2 on medium.com works just fine in all of this browsers.
所以，我的问题是：这是怎么回事，如何解决这个问题。
So, my question is: what's going on and how to fix this?
推荐答案
您使用的杀毒软件（如Avast的），并检查它的HTTPS流量？
Are you using antivirus software (e.g. Avast) and is it inspecting your HTTPS traffic?
它表现得像个MITM所以您将它连接它这样做，并把它连接到真正的网站。如果他们只支持HTTP / 1（据我所知，他们只能做），那么这将解释这一点。但奇怪的是没有为中等，除非你有一个例外，这一点。
It does this by acting like a MITM so you connect it it and it connects to the real website. And if they only support http/1 (which as far as I know they only do) then that would explain this. Though oddly not for for Medium unless you have an exception for this.
应该是很容易通过访问该网站的时候，看它是否是出台的本地服务器的Avast在看HTTPS证书进行检查。
Should be easy enough to check by looking at the HTTPS cert when visiting the site to see if it was "issued" by your local Avast server.
如果不是那么建议你看看你的密码作为HTTP / 2是挑剔它使用哪些。什么奇怪的显示在 https://www.ssllabs.com/servertest 为您的网站？它是使用Chrome的密码是什么？
If not that then suggest you look at your ciphers as HTTP/2 is picky about which ones it uses. Anything weird showing on https://www.ssllabs.com/servertest for your site? What cipher is it using for Chrome?
这篇关于为什么HTTP / 2上的特定网站在FF的作品，但在Chrome，IE和边缘相同的Windows 10的计算机上不起作用？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
