Nginx HTTP/2 + SPDY PATCH for NGINX 1.10 + NGINX 1.11

Despite the fact that Google has stopped there SPDY support in Chrome,
I still get a lot of visitors with HTTP/2 non supported browsers.

For example small Apple devices as iPhone, iPad, a lot fragmented Android's.

---

And also Windows systems < 10 with Internet Explorer etc.
These legacy devices can't use HTTP/2 but are SPDY supported.

Unfortunately the patch of Cloudflare is only usable with Nginx 1.9.7.
Nginx 1.9.7. is outdated, insecure and not updated since 17 Nov 2015.

The simplest solution would be support for both protocols in a transitional situation.
Using an up-to-date Nginx application.

And it might not be today, no no its gonna be tonight.
Thanks to Felix Bünemann it is possible right now.

Felix Bünemann ported Cloudflare's HTTP/2 + SPDY PATCH to work with Nginx 1.10.* and above.
I did some quick tests and it works fine for me with both Nginx 1.10 and 1.11.

server offers:
* h2
* spdy/3.1
* http/1.1

 

Works fine but time will tell as the patch is running here for a few days now.
Used diff to compare the Cloudflare and Felix patch.
Seems as he rectify the changes at the network protocol code between Nginx 1.9.7 and Nginx 1.10.*

About visitors.
As your site is focusing on new software, compiling, installing etc, your main visitors are trained
IT guys if you ask me. Those group of visitors usually use up-to-date computer software.

The big group of mainstream users won't surf trough sites like this.
The can't understand a word what is written and normally don't use up-to-date software,
unless its pushed automatically.

Main users on my SPDY enabled sites are mobile users via Android (version 4.4 and 5, iPhone and iPad.)

 

I am sure, as written before the visitors are non IT.
The don't use the latest of the latest but what comes out of the box.
About the can i use website, the website is made for developers to see what is possible, not for mainstream ordinary visitors.

It's not about which software + options and functions are available but which software they are using.
Differs per website per market and target audience.

Hence the big differences between us.

 

you are absolutely right, I checked Analytics.

When SPDY would not be necessary.
I'm not using it.
Every patch to mutch could break or make Nginx unstable and that's what nobody wants.
Fact is that most visitors here are Apple mobilers + Windows 7 (ie8-11) so thats the main focus and target for me.

 

Are you testing the patch also?

 

HTTP/2 with dual certificate (RSA and ECDSA)?

 

As written before the HTTP/2 + SPDY PATCH for NGINX 1.10 + NGINX 1.11 is working fine here.
It looks like a solid patch because there are more users reporting the same:

Hans van Eijsden - Thank you very much! Works great, also on 1.11.0!
John Graham-Cumming / programmer of Cloudfare - This is cool. Can you submit an updated patch instead so we can keep the old one around as well?
frostieDE - Works fine against nginx 1.11.0 and OpenSSL 1.0.2h (with ChaCha20 patch). I am building nginx as an Ubuntu 16.04 package.
kn007 - nginx 1.11.1 test pass

 

I forgot to mention.
Working fine with dual certificate (RSA and ECDSA) Nginx 1.11.1.
Old browser users will get RSA + SPDY, modern based browsers will get ECDSA with HTTP/2.

 

In addition to Felix Bünemann's 1st patch (You can find a link above).
An update is available.

Change log:
"additional fixes to re-enable deprecated spdy directives and fix compilation with http_v2 module enabled and spdy disabled."

[PATCH] Add SPDY support back to Nginx 1.10 with HTTP/2 and SPDY dual support

 

You need to patcht the Nginx source before building it.
patch < ../nginx_1_9_15_http2_spdy.patch

Because this goes beyond Centminmod, you should build Nginx manually.

 

Cloudflare's SPDY patch works only with Nginx 1.9.7.
Felix Bünemann ported it to Nginx 1.10 - 1.11.
This thread is all about Felix Bünemann's patch.