HTTP2 support
See original GitHub issueContext
HTTP2 is the new standard and it looks very promising.
Alternatives
There are no alternatives yet.
Has the feature been requested before?
Nope.
If the feature request is accepted, would you be willing to submit a PR?
Currently I’m busy with http2-wrapper
(HTTP2, just with the usual HTTP1 API). It depends. If you want me to do it now, I can’t. If you let me do it a month later, sure.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:13
- Comments:8 (4 by maintainers)
Top Results From Across the Web
HTTP/2 protocol | Can I use... Support tables for HTML5, CSS3 ...
HTTP/2 is only supported over TLS (HTTPS). See also the precursor of HTTP/2, the SPDY protocol, which has been deprecated and removed from...
Read more >HTTP/2 - Wikipedia
Most major browsers had added HTTP/2 support by the end of 2015. ... About 97% of web browsers used have the capability. ......
Read more >HTTP/2 Frequently Asked Questions
In browsers, HTTP/2 is supported by the most current releases of Edge, Safari, Firefox and Chrome. Other browsers based upon Blink will also...
Read more >HTTP/2 Test - Verify HTTP/2 Support - KeyCDN Tools
This test can check HTTP and HTTPS but most browsers only support HTTP/2 for HTTPS, which means you must migrate to HTTPS if...
Read more >Introduction to HTTP/2 - web.dev
HTTP/2 (or h2) is a binary protocol that brings push, multiplexing streams and frame control ... and add support for request prioritization and...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
If I may add, I think a discussion or RFC on what the API would look like to support HTTP2 might be a good first step before an actual implementation PR. I know the fundamentals of HTTP2, but I don’t use it day to day, and I don’t think Nock’s current API is sufficient. The concept of server-push alone has some gotchas when testing from the client-side.
The maintainers work on Nock in their free time and we don’t maintain a roadmap of new features. If someone is interested in making this addition we’re happy to try to help get it merged.