HTTP2 is coming

Blog about “HTTP/2 is Done”

Cool. If someone needs it, I probably can easily add it to the MBS CURL plugin.

Before you jump on your horses, just remember that the WebSocket RFC process took 3+ years to complete. Just because the author thinks it’s ready for submission to IETF doesn’t mean that it will be ratified that way.

Sure, without a server to test, it will be hard to use :slight_smile:

I was already looking for my horse… :smiley:

Guys, the SPDY protocol is currently in use. HTTP/2 is the “standardized” version of SPDY (SPDY v4)). The chromium project will substitute the SPDY engine by HTTP/2 standard version only in the v40 Chrome Browser (next year?). Right now you can enable it using the “–enable-spdy4” command-line flag (uses TLS). Having /1.1 is enough for now, can we have it? :slight_smile:

The latest IIS on Win 10 Technical Preview serves HTTP/2 (but only secured pages i.e. HTTPS).

And apparently, Firefox 36 already fully implements the HTTP / 2 protocol:

I’d be looking for SERVERS that implement it
Clients may be implementing something they’re not going to see much of

Apparently about twenty servers start to consider http/2. With the current competition between servers (and browsers), one can hope that its adoption is quite fast.

Just skimming that list, I don’t see Apache or IIS.

Unless we have a paying customer who desperately needs that feature, we will probably do nothing.
(or just use whatever someone adds to curl library with our plugin)

How to enable HTTP/2 for IIS on Windows 10 Technical Preview

If your client (browser) is connecting to the IIS server over TLS that negotiates HTTP/2 via TLS extensions, then you do not need to make any change on the server-side. This is because over TLS the h2-14 header specifying use of HTTP/2 Draft 14 is sent by default.

If on the other hand your client is sending an Upgrade header to upgrade to HTTP/2, then you need to make the change below on the server side to ensure that the Upgrade works and you end up with an HTTP/2 connection.

  1. Run regedit.exe

  2. Browse to registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HTTP\Parameters

  3. Create a new DWORD value named “DuoEnabled” (without quotes)

  4. Set its value to 1

  5. Reboot your server

Once your server and IIS site are up, connecting from an HTTP/2 aware client will negotiate an HTTP/2 connection with your server.

I found this:

For server :

[quote]Right now, both the Apache and nginx web servers support HTTP/2. nginx supports HTTP/2 natively, and Apache supports it via the mod_spdy module. Since Apache and nginx serve traffic for 66% of all active web servers, chances are good that your website’s server can support HTTP/2 right now.

If you aren’t using nginx or Apache you still have other options. There are a number of smaller, more specialized projects that support HTTP/2. You can also place a reverse proxy that support HTTP/2 like HAProxy in front of your existing web server to get the same benefit as having a web server that directly supports HTTP/2.

If you run your site through a hosting provider, check with them to see which web server version they are running. Major sites like and CloudFlare all already offer HTTP/2 support. If your provider is not yet supporting HTTP/2, let them know this is important![/quote]

(And on the wikipedia link, they indicate that IIS handle http/2 on Windows 10)

For browser:

[quote]In fact, the latest versions of all the major desktop web browsers already support HTTP/2. Chrome and Firefox has supported it for several years. Apple added support to Safari in fall of 2014 with Safari 8. IE 11 supports HTTP/2, but only if you are running Windows 8.

Similarly, there is already widespread HTTP/2 adoption on smart phones as well. Android’s older web browser, helpfully named Browser, has support HTTP/2 for several years. The current default browser for Android is Google’s Chrome browser. Mobile versions of Chrome use the same networking code as Desktop Chrome. This means that both Chrome on Android devices, as well as Chrome on iOS devices, both support HTTP/2. Apple added support to the iOS version of Safari with iOS 8.


Keep an eye on Katana server too.

The classic framework likely wont be updated for this.

The new framework relies more on the OS vendors implementations so as those are updated the new framework updates as well.

For me, for now, it’s ok. I just need http/1.1

And few of those listed on Github or wikipedia are supporting the finalized version (which still hasn’t been ratified yet)
They mostly support some draft of it

2015 is not the HTTP/2 year. It’ll only make sense by 2016 with a multitude of servers already running it. And with the negotiated fall-back to 1.1 everybody will gain extra time to update their clients for months.