# Request for HTTP/2 support
**URL:** https://discourse.nodered.org/t/request-for-http-2-support/58781
**Category:** Feature Requests
**Created:** [21 February 2022 23:23 UTC](https://discourse.nodered.org/t/request-for-http-2-support/58781 "2022-02-21T23:23:24Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)
#### Post date: [21 February 2022 23:23 UTC](https://discourse.nodered.org/t/request-for-http-2-support/58781/1 "2022-02-21T23:23:24Z")
I suspect that this is a "beyond v3" request. But it would be really good to look at supporting HTTP/2 in addition to HTTP and HTTPS (both of which are HTTP/1.1 I think).
Opening up HTTP/2 would potentially bring both performance and security benefits.
One of the issues though with HTTP/2 has previously been support for websockets. However, HTTP/2 does now have a mechanism for supporting them and I note that later versions of [Socket.IO](http://Socket.IO) also support HTTP/2. Not sure if any basic websocket libraries support HTTP/2 though which may scupper things.
[HTTP/1.1 vs HTTP/2: What's the Difference? | DigitalOcean](https://www.digitalocean.com/community/tutorials/http-1-1-vs-http-2-what-s-the-difference)
[Evolution of HTTP - HTTP | MDN](https://developer.mozilla.org/en-US/docs/Web/HTTP/Basics_of_HTTP/Evolution_of_HTTP)
[How HTTP/2 will Change The Way We Communicate? | by Vivek Shivhare | Geek Culture | Medium](https://medium.com/geekculture/how-http-2-will-change-the-way-we-communicate-6d92925b912d)
---
### Author:  [@system](https://discourse.nodered.org/u/system)
#### Post date: [22 April 2022 23:23 UTC](https://discourse.nodered.org/t/request-for-http-2-support/58781/2 "2022-04-22T23:23:41Z")
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.