New issue
Advanced search Search tips

Issue 615644 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: May 2016
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 3
Type: Bug



Sign in to add a comment

Chrome 51 No Longer Instantates HTTP/2 Connections with Nginx 1.10+

Reported by ch...@anthum.com, May 28 2016

Issue description

Chrome Version       : 51.0.2704.63
OS Version: OS X 10.11.4
URLs (if applicable) :
Other browsers tested:
  Add OK or FAIL after other browsers where you have tested this issue:
     Safari 5:
  Firefox 4.x:
     IE 7/8/9:

What steps will reproduce the problem?
1. Open DevTools and click Network tab
2. Navigate to https://www.httpvshttps.com/check-server.js
3. Inspect Request Headers for "check-server.js" 

What is the expected result?

The page should instantiate an HTTP/2 connection with my Nginx server. The page should show "var supportsLatestHTTPS='h2';", indicating that the browser established a connection with nginx.

You should also see the following H2 request headers (prefixed with colins) in the DevTools inspector:
:authority:www.httpvshttps.com
:method:GET
:path:/check-server.js
:scheme:https


What happens instead of that?

An H2 connection is not established.  The page is blank (indicating that a non-H2 connection is established) and the H2 headers are not shown.

Please provide any additional information below. Attach a screenshot if
possible.

I'm running nginx 1.11.0 and this worked fine on Chrome 50. It broke when I upgraded to Chrome 51. I also confirmed this on my friend's computer running Chrome 50.  Firefox 46.0.1 and Safari 9.1 correctly establish H2 connections and show "var supportsLatestHTTPS='h2';"

H2 connections also fail if I downgrade nginx to previous versions (1.10.0) 

UserAgentString: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.63 Safari/537.36



 
chrome-problem.png
519 KB View Download
chrome-ok.png
733 KB View Download
firefox-ok.png
419 KB View Download

Comment 1 by ch...@anthum.com, May 28 2016

Just realized a protocol column better exemplifies the problem
chrome-51-problem.png
133 KB View Download

Comment 2 by ch...@anthum.com, May 28 2016

chrome-51-problem2.png
232 KB View Download

Comment 3 by ch...@anthum.com, May 28 2016

My server is running OpenSSL 1.0.1f
Status: WontFix (was: Unconfirmed)
Relevant thread from blink-dev on removal: https://groups.google.com/a/chromium.org/forum/#!msg/blink-dev/Qroz7eyCzRs/vbeq4oaYDQAJ

Closing as working as expected.

Comment 5 by ch...@anthum.com, May 28 2016

Thanks.  I will update server from OpenSSL 1.0.1 to 1.0.2 as instructed in http://nginx.org/en/docs/http/ngx_http_v2_module.html

Sign in to add a comment