Examples of Node webserver engines using HTTP/2 protocol
Last updated on: June 26th, 2020
| Framework | HTTP/2 support | comment |
|---|---|---|
| Adonis | Yes | |
| Express | Using SPDY | HTTP/2 support PR |
| Hapi | Yes | |
| Koa | Yes | |
| LoopBack | No | Uses Express but server configuration is limited |
| Nest | Using SPDY | Uses Express |
| Restana | Yes | |
| Restify | Yes | |
| Sails | No | Uses Express but server configuration is limited |
| Strapi | No | Uses Koa but server configuration is limited |
| Total | Using SPDY | HTTP2 support will be added in a futere release (v4) |
A reverse proxy would be reasonable if the framework doesn't support HTTP/2 but it may not always be a desired thing to add. Adding a reverse proxy means having another dependency to work with and may limit request handling if it's not correctly configured. Some applications (like gateways or load balacers) made in Node require a direct connection to the client and thus profit by using frameworks that work with Node's native HTTP modules.
Google has a detailed page about this.
While it fixes workarounds made in HTTP/1.1 it isn't backwards compatible with HTTP/1.x. Node has a compatibility API that still allows HTTP/1.x connections, as does the SPDY package.
Cool you found a framework that I haven't found or tested yet, or maybe I've had issues with it for some reason. If you'd like to see this framework added, please check Issues for more information or create a new one if it doesn't exist yet.