DEV Community

Cover image for The Power of Pure HTTP – screen share, real-time messaging, SSH and VNC
Ryo Ota
Ryo Ota

Posted on • Updated on

The Power of Pure HTTP – screen share, real-time messaging, SSH and VNC

Hi all. Today, I'd like to show you the power of pure HTTP stream, which allows us to do screen sharing, video chatting, real-time text messaging, SSH, VNC, and so on. The demo videos below show SSH and VNC over pure HTTP. Let's dive into this!


HTTP is everywhere for everyone and everything, which allows us to communicate in any situation. HTTP is one of the most mature protocols and wildly used. You can find HTTP in web browser in personal computers including Windows, Mac and Linux, smartphones and tablets including Android, iPhone and iPad, curl, wget commands in your terminal, some IoT devices, automation tools such as Shortcuts iOS app and Microsoft Flow, Web Hooks and so on. Additionally, HTTP is an evolving protocol as HTTP/2, HTTP/3 and getting faster.

Usuary, an HTTP request has a short life, used for fetching HTML/CSS/JavaScript, media and API requests. So, this post introduces long-life HTTP request, which does real-time communications over pure HTTP stream without WebSocket and WebRTC.

Piping Server

I made Piping Server, which allows us to transfer data between every device.

GitHub logo nwtgck / piping-server

Infinitely transfer between every device over pure HTTP with pipes or browsers

Piping Server

npm CodeFactor Build status GitHub Actions Docker Automated build

Infinitely transfer between every device over HTTP/HTTPS
Piping Server hello


Piping Server is simple. You can transfer as follows.

# Send
echo 'hello, world' | curl -T -
Enter fullscreen mode Exit fullscreen mode
# Get
curl > hello.txt
Enter fullscreen mode Exit fullscreen mode

Piping Server transfers data to POST /hello or PUT /hello into GET /hello. The path /hello can be anything such as /mypath or /mypath/123/. A sender and receivers who specify the same path can transfer. Both the sender and the recipient can start the transfer first. The first one waits for the other.

You can also use Web UI like on your browser. A more modern UI is found in, which supports E2E encryption.


The most important thing is that the data are streamed. This means that you can transfer any data infinitely. The demo below transfers an infinite text stream with seq inf.

infnite text stream


Piping Server is simple. A sender and recipient who specify the same path such as /hello can transfer. The image below is the concept of transfer.

The concept of Piping Server

The image shows the sender who POSTs /mypath and the recipient GETs /mypath can transfer. Both the sender and the recipient can start the transfer first. The first one waits for the other. Both POST and PUT methods are the same in Piping Server.

You can transfer a text by using fetch() in JavaScript like below.

// Send
fetch("", {
  method: "POST",
  body: "hello, world"
Enter fullscreen mode Exit fullscreen mode
// Get
const res = await fetch("");
console.log(await res.text());
// => "hello, world"
Enter fullscreen mode Exit fullscreen mode

You can also use curl command like below.

Piping Server text transfer

You can also transfer binary data such as an image and a video like below. As you can see, the recipient just opened the URL on the browser to get the image.

Piping Server image transfer

HTTP is everywhere. So we can transfer data freely without any extra tools.

Infinitely transfer

The most notable feature of Piping Server is allowing you to transfer infinite data. The demo below shows inputting text streams into the web browser.

sender: curl, receiver: browser

Send folder

You can transfer a folder (a directory), which has multiple files as follows.

Piping Server directory sending

# Send folder
tar c ./mydir | curl -T -
Enter fullscreen mode Exit fullscreen mode
# Get folder
curl | tar xv
Enter fullscreen mode Exit fullscreen mode

The files are packing while uploading in the sender and unpacking while downloading in the recipient. Stream makes this possible without creating a temporary file.

It is easy to end-to-end encrypt your data and transfer as follows.

  • send: ... | openssl aes-256-cbc | curl -T ...
  • get: curl ... | openssl aes-256-cbc -d

It is also easy to reduce the size by compression as follows.

  • send: ... | gzip | curl -T ...
  • get: curl ... | zcat

You can transform data as you want such as gpg, zip or tools invented in the future. Combining pipe is efficient in terms of both time and memory. Unix pipe is an amazing way to combine software. The name of Piping Server is derived from Unix pipe.

The most common use case of Piping Server is a file transfer. For transferring files, you can use Piping UI, which allows you to transfer securely with end-to-end encryption over many devices.

Transfer huge data for a long time

Here are simple experiments to transfer data over HTTP using local and remote Piping Server.

The demo video below shows 45TB is transferred for 2,092 hours (87 days) over HTTP via remote Piping Server, using cat /dev/zero | curl -T- ....

remote Piping Server 45TB, 87 days

The image below shows transferred 1,110TB (≈ 1PB) for 64 days over HTTP via local Piping Server.

local Piping Server 1110TB, 64 days

These experiments show a huge amount of data can be continuously transferred over a single HTTP request and a single HTTP request lives long enough.

Infinite stream for Web browser

Infinite stream sending over HTTP had come to Web browser at last!

Google Chrome 85 or above has the feature as origin trial. Open chrome://flags and enable "Experimental Web Platform features" as follows

Experimental Web Platform features

Other main browsers such as Firefox and Safari are also interested in this feature.

Uploading a Request made from a ReadableStream body by yutakahirano · Pull Request #425 · whatwg/fetch

In a nutshell, this feature allows us to send ReadableStream as follows.

fetch("", {
  method: "POST",
  body: <ReadableStream here!>
Enter fullscreen mode Exit fullscreen mode

Simple text messaging

Here is a simple text messaging on Web browser with fetch() and ReadableStream.

sender: browser, receiver: browser

The code below creates ReadableStream from user input and sends the input stream to Piping Server. The recipient just opens the URL on the browser and sees streamed text messages.

const readableStream = new ReadableStream({
  start(ctrl) {
    const encoder = new TextEncoder();
    window.myinput.onkeyup = (ev) => {
      if (ev.key === 'Enter') {
        ctrl.enqueue(encoder.encode('\n')); = '';

fetch("", {
  method: 'POST',
  body: readableStream,
  headers: { 'Content-Type': 'text/plain;charset=UTF-8' },
  allowHTTP1ForStreamingUpload: true,
Enter fullscreen mode Exit fullscreen mode


allowHTTP1ForStreamingUpload in the code is a temporary property in Chrome to allow us to use this feature over HTTP/1.1 (see: 4c75c0c9f730589ad8d6c33af919d6b105be1462 - chromium/src - Git at Google).

Screen sharing

You can share your screen in almost the same way as the text streaming above. Get MediaStream and convert to ReadableStream and send the stream to Piping Server with fetch().

Piping Server screen sharing

The function mediaStreamToReadableStream() below converts MediaStream to ReadableStream.

(async () => {
  // Get display
  const mediaStream = await navigator.mediaDevices.getDisplayMedia({video: true});
  // Convert MediaStream to ReadableStream
  const readableStream = mediaStreamToReadableStream(mediaStream, 100);

  fetch("", {
    method: 'POST',
    body: readableStream,
    allowHTTP1ForStreamingUpload: true,

// Convert MediaStream to ReadableStream
function mediaStreamToReadableStream(mediaStream, timeslice) {
  return new ReadableStream({
      const recorder = new MediaRecorder(mediaStream);
      recorder.ondataavailable = async (e) => {
        ctrl.enqueue(new Uint8Array(await;
Enter fullscreen mode Exit fullscreen mode


The recipient just opens the HTML below with one <video> tag.

<!-- viewer -->
<video src="" autoplay muted></video>
Enter fullscreen mode Exit fullscreen mode

This way is friendy to command-line tools too. You can also view the screen with curl | ffplay -. You can also send your screen with ffmpeg command. See Capture/Desktop – FFmpeg for more info.

Voice and video chatting

For voice or video chatting, all you need to do is to replace the code, const mediaStream = above with:

// Voice
const mediaStream = navigator.mediaDevices.getUserMedia({ audio: { echoCancellation: true } })
Enter fullscreen mode Exit fullscreen mode
// video + voice
const mediaStream = navigator.mediaDevices.getUserMedia({ video: true, audio: { echoCancellation: true } })
Enter fullscreen mode Exit fullscreen mode


(video + voice:

Then, you can use the mediaStreamToReadableStream() to converts those MediaStreams to ReadableStreams to specify body: in fetch().

Video filtering

You can get MediaStream from the canvas. The function below creates a video and a canvas in memory and transforms a MediaStream to another one. JSManipulate is used. You may create a filter app like Snap Camera.

// Filter for sepia
async function sepiaMediaStream(mediaStream) {
  const memVideo = document.createElement('video');
  memVideo.srcObject = mediaStream;

  const width = memVideo.videoWidth;
  const height = memVideo.videoHeight;
  const srcCanvas = document.createElement('canvas');
  const dstCanvas = document.createElement('canvas');
  srcCanvas.width = dstCanvas.width = width;
  srcCanvas.height = dstCanvas.height = height;
  const srcCtx = srcCanvas.getContext('2d');
  const dstCtx = dstCanvas.getContext('2d');

  (function loop(){
    srcCtx.drawImage(memVideo, 0, 0, width, height);
    const frame = srcCtx.getImageData(0, 0, width, height);

    dstCtx.putImageData(frame, 0, 0);
    setTimeout(loop, 0);

  return dstCanvas.captureStream();
Enter fullscreen mode Exit fullscreen mode


(demo video:


Compress data with gzip as follows. In Chrome, you can easily compress a stream with readableStream.pipeThrough(new CompressionStream('gzip')).

const readableStream = new ReadableStream({
  pull(ctrl) {
    // random bytes
    ctrl.enqueue(window.crypto.getRandomValues(new Uint32Array(128)));
}).pipeThrough(new CompressionStream('gzip'))

fetch("", {
  method: 'POST',
  body: readableStream,
  allowHTTP1ForStreamingUpload: true,
Enter fullscreen mode Exit fullscreen mode

The sample code sends infinite random bytes with compression over Piping Server.

End-to-end encryption for infinite stream

You can safely transfer your stream even if a server is untrustable. You can encrypt any ReadableStream with the code below using OpenPGP.js.

// Encrypt ReadableStream with password by OpenPGP
async function encryptStream(readableStream, password) {
  const options = {
    message: openpgp.message.fromBinary(readableStream),
    passwords: [password],
    armor: false
  const ciphertext = await openpgp.encrypt(options);
  return ciphertext.message.packets.write();
Enter fullscreen mode Exit fullscreen mode is a demo video of end-to-end encrypted screen sharing over Piping Server.

Service Worker is used on the viewer-side. The purpose of using Service Worker is for getting a decrypted video at https://localhost:8080/e2ee_screen_share/swvideo#myvideo. Service Worker is used as a proxy. See the full code for detail:

Web browsers have Web Crypto, which can generate keys safely and do Diffie-Hellman key exchange an untrustable channel. For example, Piping UI, which is a file transfer tool, exchanges public keys and encrypts a file by using ECDH and OpenPGP.js.

Access the repository below to get other examples using fetch() upload streaming feature with Piping Server.


As you see, any data can be streamed over HTTP. So, this means a protocol can be over HTTP via Piping Server.

Why Piping Server?

There are some environments that can not release ports public. For such kind of environment, when you have the only outward-connection to HTTP/HTTPS ports, you can use SSH. A possible example is for GitHub Actions, which does not support SSH debug like CircleCI (see: SSH in GitHub Actions over Piping Server).

SSH client in JavaScirpt

I found a wonderful project, SSHy whose JavaScript speaks SSH. The data communication is over WebSocket, so I just need to switch WebSocket to HTTP with fetch(). Unfortunately, although SSHy is not actively maintained now, this is a perfect fit for my proof of concept to speak SSH over HTTP using Piping Server. We could port OpenSSH by using Emscripten, write Rust and compile to Web Assembly, or do something in the future.

By using SSHy, it is possible to SSH with only Web browser and Piping Server. The data streamed to Piping Server is securely encrypted since the communication is SSH.

How to SSH over Piping Server?

Create two sets of connections over Piping Server for duplex communication. One of them is for sending data to your peer. The other one is for receiving data from your peer. On HTTP/2, multiple HTTP requests are bundled into one TCP connection.

The command below is an example to forward 22 port over HTTP via Piping Server. This way was proposed by @Cryolite in a Japanese great post The data to the 22 port is downloading from /path1 and the data from the 22 port is uploading to /path2.

# server-host
socat 'EXEC:curl -NsS https\://!!EXEC:curl -NsST - https\://' TCP:
Enter fullscreen mode Exit fullscreen mode

The way makes possible NAT traversal without releasing port public over HTTP.

The command below creates the tunnel with the command above. The 22 port is forwarded to 31376 port in your another machine.

# client-host
socat TCP-LISTEN:31376 'EXEC:curl -NsS https\://!!EXEC:curl -NsST - https\://'
Enter fullscreen mode Exit fullscreen mode

You can do ssh -p 31376 <user>@localhost in the machine in another terminal. This is a versatile way to forward a port to another device, not only SSH.

Transport implementations of SSHy

The implementation below sends bytes over WebSocket.
ws, WebSocket instance has a user-defined method, sendB64() and send Base64-encoded string. A proxy server called stuicey/wsproxy is used, which is for proxying WebSocket to TCP (in this case SSH).

The implementation below receives bytes over WebSocket.

SSH over Piping Server

These sending and receiving parts are replaced fetch() and a way of using Piping Server. The code below is the replaced implementation.

The application is called Piping SSH. Here is a demo video. In it, logging in Ubuntu machine from the web browser and type ls and htop command.
SSH over Piping Server

TIPS: Keep-alive of SSH

In Chrome, an HTTP request is stopped when no bytes arrived for 60 seconds. To resolve the issue, you can set /etc/ssh/sshd_config as follows in your SSH server setting.

# /etc/ssh/sshd_config
# ...
ClientAliveInterval 20
ClientAliveCountMax 3
# ...
Enter fullscreen mode Exit fullscreen mode


VNC (Virtual Network Computing) is widely used for controlling the computer remotely.

Here is the demo video. The front window is a Chrome, Web browser and the back one is a controlled machine on Ubuntu on VirtualBox.

VNC over Piping Server

For Ubuntu 20.04 users, to enable VNC, you can turn on Settings > Sharing and run gsettings set org.gnome.Vino require-encryption false to avoid an error, "Failed when connecting: Unsupported security types (types: 18)".

VNC is also available for Windows. Here is a demo controlling Windows 10 from Chrome. It was more smooth on a real Windows machine since the windows machine in the demo below was running on VirtualBox. UltraVNC is running on the Windows machine.

Piping VNC controlling Windows 10

The fetch-uploading feature is also available on Android Chrome. The demo below controls Windows 10 by an Android smartphone.

Piping VNC controlled by Android

For windows users, you can a download tunneling tool over Piping Server here: It is convenient to create a simple .bat file as follows.

.\piping-tunnel server -p 5900 path1 path2
Enter fullscreen mode Exit fullscreen mode

piping-tunnel has the same feature of the socat + curl command. For mac users, you can install by brew install nwtgck/piping-tunnel/piping-tunnel.

How it works

The application is fully based on noVNC, which is a VNC client written in JavaScript. Only transport implementations are replaced with the way of using fetch and Piping Server instead of WebSocket.

Here is the diff for replacing WebSocket transportation with fetch and Piping Server.

Network in Web browser

Here is the network in the Chrome DevTools. There are only two pure HTTPS connections. v86 is uploading and 7vk is downloading. As you can see the download size of v86 is increasing. Although 7vk is uploading, the view in the current Chrome says "pending".

Piping VNC network

fetch() upload streaming

I have been following this feature. Here are useful links to get information about the fetch() upload streaming feature.

Public Piping Server

Here are public Piping Servers.

Self-hosted Piping Server

Run Piping Server on http://localhost:8080 as follows using Docker.

docker run -p 8080:8080 nwtgck/piping-server
Enter fullscreen mode Exit fullscreen mode

Single binaries are also available on

Here are easier ways to get public your Piping Server is to use Glitch and Runkit.

Piping Server with JWT authentication

To restrict users to use Piping Server, you can use with an example using Auth0.

Piping Server in Rust

Piping Server is also written in Rust. This is the fastest Piping Server now.


Base posts

Here are my posts based on this post.


The link below is the repository of Piping Server.

Get more information from the link below about Piping Server such as end-to-end encrypted file transfer, with basic auth, real-time drawing and so on.

Top comments (23)

codr profile image
Ilya Nevolin

Wonderful, I love all of this!

Remote control for a Windows machine would a great addition though, not sure how realistic that would be to implement, guess I'll have to use Teamviewer/AnyDeks for now.

Another thing that spikes my interest is SSH in the browser, but I'm using key pairs instead of user:pass method, is that possible with this?

pratikdhaboo profile image
Pratik Dhaboo

May be we can use robot.js alongside the screen share to transmit mouse and keyboard events.

cubiclesocial profile image

For SSH in the browser, yes, it is possible to use SSH keys. I support both methods in File Tracker:

It uses a combination of (WebSocket-based):

And the beta async support from:

To provide two-way, async communication with a SSH host.

wick3drose profile image

This looks very interesting. I gave it a star on Github and I'm going to follow it but I just read a bit about simple text messaging quickly. I tested hello world and got it to work with echo/curl but how would the Android user know to open the browser without receiving a link?

marataziat profile image

Very cool! Websockets sucks because you need to do 2 things to sync the user: rest api request to get the initial data, and websocket connection to receive events. So you need to do 2 things to keep the user in sync. You can not push initial data via websocket when user connects because of websocket data framing.

This is also a good replacement for SSE.

I also hope http 3 support will be there soon, so there will be more stuff to explore for real time apps.

sm0ke profile image

Unconventional niceeee ...

cubiclesocial profile image

This is fairly reminiscent of my PHP Cool File Transfer project where I did something similar a few years ago:

One client basically creates a mini-TCP server inside a PHP script on the server and another client somewhere else connects to the mini-TCP server and receives the file as a direct transfer. PHP emits a byte every second to keep the connection alive for the person who is sending the file until the second client connects and accepts or rejects the file. If the file is accepted, then it starts transferring. The web server doesn't store any data - it just sends the data to the other side. The setup of a temporary TCP/IP server per file is somewhat exotic.

There is a slight gotcha with the approach: A GET method caller never finishes as can be seen in the "Simple text messaging" example for Piping Server where the loading indicator never stops spinning. That means onload won't fire in that case. In the instance of a file download, the download manager takes over and handles the request. The solution is to wait until the page has finished loading and then make a XHR request.

mickeyklai profile image

Very good and informative article!
Thank you🙏

One question that popped into my mind during reading this is wether it's possible to transport tcp over Piping server, similary to ssh over http scenario?

khuongduybui profile image
Duy K. Bui

I can see a lot of potentials in this approach. Thanks for the detailed post and ready-to-use sample resources.

I have a few questions:

  • What would be the strategy to handle disconnect / reconnect to guarantee no loss of data?
  • From what I understand, we can easily support multi-poster and multi-getter against the same "stream" without complications. Is that correct? Are there any pitfalls I have not recognized?
mikaelgramont profile image
Mikael Gramont

What a cool project.
That's the nice thing about tools that the leverage existing web ecosystem, the results can be really impressive while at the same time everyone is like "wait, yeah, of course, that should have been obvious".

amissine profile image
Alec Missine

Great work, Ryo! Thanks for sharing!

jianwu profile image
jianwu • Edited

Nice work and great blog. Is it possible to implement peer to peer streaming, so the data traffic won't pass through server.

awsonly1 profile image

Nice work and interesting. Lot of depth in the article !!

m4r4v profile image

Absolutely outstanding!!

Great article, very well written, useful and approachable.

Thanks you!!

shaikh profile image
Javed Shaikh

Awesome 👏🏼. I am going to give it a try.

king11 profile image
Lakshya Singh

I am in awe of this project 😐 completely mind bogling

mandarvaze profile image
Mandar Vaze

This is truly an awesome project

Some comments may only be visible to logged-in visitors. Sign in to view all comments.