node-http2 | An HTTP/2 client and server implementation for node.js | Runtime Evironment library

 by   molnarg JavaScript Version: v3.3.7 License: MIT

kandi X-RAY | node-http2 Summary

kandi X-RAY | node-http2 Summary

node-http2 is a JavaScript library typically used in Server, Runtime Evironment, Nodejs applications. node-http2 has no bugs, it has no vulnerabilities, it has a Permissive License and it has medium support. You can install using 'npm i http2-75lb' or download it from GitHub, npm.

An HTTP/2 ([RFC 7540] client and server implementation for node.js. NOTE WELL This package is officially deprecated. As of node 9.0.0, there is an http2 package built-in. You should use that one instead.
Support
    Quality
      Security
        License
          Reuse

            kandi-support Support

              node-http2 has a medium active ecosystem.
              It has 1789 star(s) with 214 fork(s). There are 51 watchers for this library.
              OutlinedDot
              It had no major release in the last 6 months.
              There are 60 open issues and 110 have been closed. On average issues are closed in 160 days. There are 16 open pull requests and 0 closed requests.
              It has a neutral sentiment in the developer community.
              The latest version of node-http2 is v3.3.7

            kandi-Quality Quality

              node-http2 has 0 bugs and 0 code smells.

            kandi-Security Security

              node-http2 has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.
              node-http2 code analysis shows 0 unresolved vulnerabilities.
              There are 0 security hotspots that need review.

            kandi-License License

              node-http2 is licensed under the MIT License. This license is Permissive.
              Permissive licenses have the least restrictions, and you can use them in most projects.

            kandi-Reuse Reuse

              node-http2 releases are not available. You will need to build from source code and install.
              Deployable package is available in npm.
              Installation instructions are not available. Examples and code snippets are available.

            Top functions reviewed by kandi - BETA

            kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
            Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of node-http2
            Get all kandi verified functions for this library.

            node-http2 Key Features

            No Key Features are available at this moment for node-http2.

            node-http2 Examples and Code Snippets

            No Code Snippets are available at this moment for node-http2.

            Community Discussions

            QUESTION

            Socket.io perpetual disconnection on HTTP 2 due to missing Keep-Alive headers
            Asked 2020-Nov-26 at 07:25

            After having developed my application in an unsecured context using HTTP 1.1, I have now deployed it to a HTTP 2 server using HTTPS. All fine and dandy. For 30 seconds... :)

            After that, the socket disconnects and connects again. And again. And again.

            What I saw missing from the server response are the Connection: keep-alive and Keep-Alive: timeout=5 headers that I get on my HTTP 1.1 server. The code is absolutely identical and communication does work just fine.

            I suppose socket.io has some smart way of working over HTTP 2 but I couldn't find anything about this in the documentation.

            It's also interesting that the client DOES request the keep-alive header, despite it running on HTTP 2. But alas, nothing is returned and the socket disconnects :(

            I noticed somebody tried using SPDY via Express:

            Getting socket.io, express & node-http2 to communicate though HTTP/2

            I would consider this as a possible solution, but I would like this to work without SPDY as well.

            ...

            ANSWER

            Answered 2020-Nov-26 at 07:25

            After encountering the EXACT same issue when using the WebSocket object in the browser, I dug deeper and found this in the documentation of the Google Load Balancer service we're using:

            The timeout for a WebSocket connection depends on the configurable backend service timeout of the load balancer, which is 30 seconds by default. This timeout applies to WebSocket connections regardless of whether they are in use. For more information about the backend service timeout and how to configure it, see Timeouts and retries.

            https://cloud.google.com/load-balancing/docs/https?fbclid=IwAR2Qugtlyvd05VteGWk2RCevebUJrHTHyW9RHAwYiPxudM6qOovaa2Zdqpk

            Check this article for more info about how to config your Load Balancer to correctly handle WebSockets:

            https://medium.com/johnjjung/how-to-use-gcp-loadbalancer-with-websockets-on-kubernetes-using-services-ingresses-and-backend-16a5565e4702

            Source https://stackoverflow.com/questions/64902100

            Community Discussions, Code Snippets contain sources that include Stack Exchange Network

            Vulnerabilities

            No vulnerabilities reported

            Install node-http2

            You can install using 'npm i http2-75lb' or download it from GitHub, npm.

            Support

            The developer documentation is generated from the source code using docco and can be viewed online [here](http://molnarg.github.io/node-http2/doc/). If you’d like to have an offline copy, just run npm run-script doc.
            Find more information at:

            Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items

            Find more libraries
            CLONE
          • HTTPS

            https://github.com/molnarg/node-http2.git

          • CLI

            gh repo clone molnarg/node-http2

          • sshUrl

            git@github.com:molnarg/node-http2.git

          • Stay Updated

            Subscribe to our newsletter for trending solutions and developer bootcamps

            Agree to Sign up and Terms & Conditions

            Share this Page

            share link