Run HTTP over UDP and Bring Web in Peer or P2P styles :

Node.js v12.x API compatible Run HTTP and HTTPS over UDP, taking UDP high performance Support multi-process/thread UDP server by utilizing multi-cores' CPU Configurable Congestion Control Per-Socket network performance monitor Extend client/central server style web service transparently Easy to use API, reuse existing http/web and node.js technology Support Windows/Linux/OSx, RaspberryPi, Android

Programming language: JavaScript
License: GNU General Public License v3.0 or later
Tags: Nodejs     HTTP     Http-over-udp    
Latest version: v2015.11.25

nodejs-httpp alternatives and similar modules

Based on the "HTTP" category.
Alternatively, view nodejs-httpp alternatives based on common mentions on social networks and blogs.

Do you think we are missing an alternative of nodejs-httpp or a related project?

Add another 'HTTP' Module


nodejs-httpp - Run HTTP over UDP based transport and Bring Web in Peer or P2P styles

test-linux test-macOS build-windows

  • main js modules: udt.js, httpp.js, udts.js and httpps.js, that's compatible to net.js,http.js,tls.js and https.js

  • HTTP over UDP Wiki page


  • Node.js v12.x API compatible
  • Support UDT(UDP-based transport) protocol
  • Run HTTP and HTTPS over UDT over UDP, taking UDP high performance
  • Support high-performance multi-process/multi-thread UDP server by utilizing multi-cores' CPU
  • Configurable Congestion Control
  • Per-Socket network performance monitor
  • Extend client/central server style web service transparently
  • Easy to use API, reuse existing http/web and node.js technology
  • Support Windows/Linux/OSx, RaspberryPi, Android


  • Add more test cases
  • Improve documents
  • RFC protocol draft

third-party source

Support us

  • Welcome contributing on document, codes, tests and issues

To checkout the sourcecode:

git clone --recursive https://github.com/InstantWebP2P/nodejs-httpp.git

Build on Linux with Docker



packaging and start Node.js REPL:


To build on other platforms


make install



Resources for Newcomers

Node.js is an open-source, cross-platform, JavaScript runtime environment. It executes JavaScript code outside of a browser. For more information on using Node.js, see the Node.js Website.

The Node.js project uses an [open governance model](./GOVERNANCE.md). The OpenJS Foundation provides support for the project.

This project is bound by a Code of Conduct.

Table of Contents


Looking for help? Check out the [instructions for getting support](.github/SUPPORT.md).

Release Types

  • Current: Under active development. Code for the Current release is in the branch for its major version number (for example, v10.x). Node.js releases a new major version every 6 months, allowing for breaking changes. This happens in April and October every year. Releases appearing each October have a support life of 8 months. Releases appearing each April convert to LTS (see below) each October.
  • LTS: Releases that receive Long-term Support, with a focus on stability and security. Every even-numbered major version will become an LTS release. LTS releases receive 12 months of Active LTS support and a further 18 months of Maintenance. LTS release lines have alphabetically-ordered codenames, beginning with v4 Argon. There are no breaking changes or feature additions, except in some special circumstances.
  • Nightly: Code from the Current branch built every 24-hours when there are changes. Use with caution.

Current and LTS releases follow Semantic Versioning. A member of the Release Team signs each Current and LTS release. For more information, see the Release README.


Binaries, installers, and source tarballs are available at https://nodejs.org/en/download/.

Current and LTS Releases


The latest directory is an alias for the latest Current release. The latest-codename directory is an alias for the latest release from an LTS line. For example, the latest-carbon directory contains the latest Carbon (Node.js 8) release.

Nightly Releases


Each directory name and filename contains a date (in UTC) and the commit SHA at the HEAD of the release.

API Documentation

Documentation for the latest Current release is at https://nodejs.org/api/. Version-specific documentation is available in each release directory in the docs subdirectory. Version-specific documentation is also at https://nodejs.org/download/docs/.

Verifying Binaries

Download directories contain a SHASUMS256.txt file with SHA checksums for the files.

To download SHASUMS256.txt using curl:

$ curl -O https://nodejs.org/dist/vx.y.z/SHASUMS256.txt

To check that a downloaded file matches the checksum, run it through sha256sum with a command such as:

$ grep node-vx.y.z.tar.gz SHASUMS256.txt | sha256sum -c -

For Current and LTS, the GPG detached signature of SHASUMS256.txt is in SHASUMS256.txt.sig. You can use it with gpg to verify the integrity of SHASUM256.txt. You will first need to import the GPG keys of individuals authorized to create releases. To import the keys:

$ gpg --keyserver pool.sks-keyservers.net --recv-keys DD8F2338BAE7501E3DD5AC78C273792F7D83545D

See the bottom of this README for a full script to import active release keys.

Next, download the SHASUMS256.txt.sig for the release:

$ curl -O https://nodejs.org/dist/vx.y.z/SHASUMS256.txt.sig

Then use gpg --verify SHASUMS256.txt.sig SHASUMS256.txt to verify the file's signature.

Building Node.js

See [BUILDING.md](BUILDING.md) for instructions on how to build Node.js from source and a list of supported platforms.


For information on reporting security vulnerabilities in Node.js, see [SECURITY.md](./SECURITY.md).

Contributing to Node.js

Current Project Team Members

For information about the governance of the Node.js project, see [GOVERNANCE.md](./GOVERNANCE.md).

TSC (Technical Steering Committee)

<!--lint disable prohibited-strings-->

TSC Emeriti


Collaborator Emeriti

Collaborators follow the [Collaborator Guide](./doc/guides/collaborator-guide.md) in maintaining the Node.js project.

Release Keys

Primary GPG keys for Node.js Releasers (some Releasers sign with subkeys):

To import the full set of trusted release keys:

gpg --keyserver pool.sks-keyservers.net --recv-keys 4ED778F539E3634C779C87C6D7062848A1AB005C
gpg --keyserver pool.sks-keyservers.net --recv-keys 94AE36675C464D64BAFA68DD7434390BDBE9B9C5
gpg --keyserver pool.sks-keyservers.net --recv-keys 71DCFD284A79C3B38668286BC97EC7A07EDE3FC1
gpg --keyserver pool.sks-keyservers.net --recv-keys 8FCCA13FEF1D0C2E91008E09770F7A9A5AE15600
gpg --keyserver pool.sks-keyservers.net --recv-keys C4F0DFFF4E8C1A8236409D08E73BC641CC11F4C8
gpg --keyserver pool.sks-keyservers.net --recv-keys DD8F2338BAE7501E3DD5AC78C273792F7D83545D
gpg --keyserver pool.sks-keyservers.net --recv-keys A48C2BEE680E841632CD4E44F07496B3EB3C1762
gpg --keyserver pool.sks-keyservers.net --recv-keys B9E2F5981AA6E0CD28160D9FF13993A75599653C

See the section above on Verifying Binaries for how to use these keys to verify a downloaded file.

Other keys used to sign some previous releases: