websocat - Websocket proxy, socat-style

  •        168

Note: Currently SSL-enabled version may be unbuildable on systems with newer libssl because of hard reliance on old versions of dependencies. Wait for websockat 1.0.0 with async and updated deps. Pre-built binaries for Linux (usual and musl), Windows, OS X and Android (ARM) are available on the releases page. Most are built without SSL support, so can't connect to secure wss:// websockets, only ws://.

https://github.com/vi/websocat

Tags
Implementation
License
Platform

   




Related Projects

WebSocket-Node - A WebSocket Implementation for Node.JS (Draft -08 through the final RFC 6455)

  •    Javascript

This is a (mostly) pure JavaScript implementation of the WebSocket protocol versions 8 and 13 for Node. There are some example client and server applications that implement various interoperability testing protocols in the "test/scripts" folder. For a WebSocket client written in ActionScript 3, see my AS3WebScocket project.

Websocket - The Hoa\Websocket library.

  •    PHP

Hoa is a modular, extensible and structured set of PHP libraries. Moreover, Hoa aims at being a bridge between industrial and research worlds. This library allows to manipulate the WebSocket protocol and proposes a server and a client. It supports two specifications RFC6455 and Hybi (at the same time).

jetfire - WebSocket (RFC 6455) client library for iOS & OS X

  •    Objective-C

WebSocket RFC 6455 client library for iOS and OSX. Jetfire is a conforming WebSocket (RFC 6455) client library in Objective-C for iOS and OSX.

SwiftWebSocket - Fast Websockets in Swift for iOS and OSX

  •    Swift

Conforming WebSocket (RFC 6455) client library for iOS and Mac OSX.SwiftWebSocket passes all 521 of the Autobahn's fuzzing tests, including strict UTF-8, and message compression.

Starscream - Websockets in swift for iOS and OSX

  •    Swift

Starscream is a conforming WebSocket (RFC 6455) client library in Swift. First thing is to import the framework. See the Installation instructions on how to add the framework to your project.


WebSocket-for-Python - WebSocket client and server library for Python 2 and 3 as well as PyPy (ws4py 0

  •    Python

Python library providing an implementation of the WebSocket protocol defined in RFC 6455. Read the documentation for more information.

gwsocket - fast, standalone, language-agnostic WebSocket server RFC6455 compliant

  •    C

gwsocket is a simple, standalone, language-agnostic, RFC6455 compliant WebSocket Server, written in C. It sits between your application and the client's browser, giving fast bidirectional communication between these two with ease and flexibility. Very simple, just redirect the output from your application (stdout) to a file (named pipe) and let gwsocket transfer the data to the browser — That's it.

easywsclient - A short and sweet WebSocket client for C++

  •    C++

Easywsclient is an easy and powerful WebSocket client to get your C++ code connected to a web stack right away. It depends only on the standard libraries. It is compatible with modern C++11 std::function and lambda, if they're available (it's not required though). RFC 6455 Version 13 WebSocket is supported. Version 13 is compatible with all major, modern WebSocket implementations, including Node.js, and has been a standard since December 2011. Rationale: This library is intended to help a C++ project start using WebSocket rapidly. This small library can easily be thrown into an existing project. For complicated builds that you can't figure out right away, you can even cheat by piggy-backing the .cpp file into one of the project's existing files. Yes, WebSocket is that awesome enough to warrant getting it integrated into your project! This project imposes no special interface requirements, and can work happily with new C++11 features or with older C++ projects.

WebSocket-Node - A WebSocket Implementation for Node.JS (Draft -08 through the final RFC 6455)

  •    Javascript

A WebSocket Implementation for Node.JS (Draft -08 through the final RFC 6455)

vpn-ws - A VPN system over websockets

  •    C

This is the client/server implementation of a layer-2 software switch able to route packets over websockets connections. A client creates a tap (ethernet-like) local device and connects to a websocket server (preferably over HTTPS). Once the websocket handshake is done, every packet received from the tuntap will be forwarded to the websocket server, and every websocket packet received from the server will be forwarded to the tuntap device.

faye-websocket-node - Standards-compliant WebSocket client and server

  •    Javascript

This is a general-purpose WebSocket implementation extracted from the Faye project. It provides classes for easily building WebSocket servers and clients in Node. It does not provide a server itself, but rather makes it easy to handle WebSocket connections within an existing Node application. It does not provide any abstraction other than the standard WebSocket API. It also provides an abstraction for handling EventSource connections, which are one-way connections that allow the server to push data to the client. They are based on streaming HTTP responses and can be easier to access via proxies than WebSockets.

WebSocket++ - C++ Websocket client/server library

  •    C++

WebSocket++ is a header only C++ library that implements RFC6455 The WebSocket Protocol. It allows integrating WebSocket client and server functionality into C++ programs. It uses interchangeable network transport modules including one based on raw char buffers, one based on C++ iostreams, and one based on Asio (either via Boost or standalone). End users can write additional transport policies to support other networking or event libraries as needed.

faye-websocket-ruby - Standards-compliant WebSocket client and server

  •    Ruby

This is a general-purpose WebSocket implementation extracted from the Faye project. It provides classes for easily building WebSocket servers and clients in Ruby. It does not provide a server itself, but rather makes it easy to handle WebSocket connections within an existing Rack application. It does not provide any abstraction other than the standard WebSocket API. It also provides an abstraction for handling EventSource connections, which are one-way connections that allow the server to push data to the client. They are based on streaming HTTP responses and can be easier to access via proxies than WebSockets.

Ratchet - Asynchronous WebSocket server

  •    PHP

A PHP library for asynchronously serving WebSockets. Build up your application through simple interfaces and re-use your application without changing any of its code just by combining different components. Shell access is required and root access is recommended. To avoid proxy/firewall blockage it's recommended WebSockets are requested on port 80 or 443 (SSL), which requires root access. In order to do this, along with your sync web stack, you can either use a reverse proxy or two separate machines. You can find more details in the server conf docs.

SocketRocket - A conforming Objective-C WebSocket client library.

  •    Objective-C

A conforming WebSocket (RFC 6455) client library for iOS, macOS and tvOS.Test results for SocketRocket here. You can compare to what modern browsers look like here.

beast - HTTP and WebSocket built on Boost.Asio in C++11

  •    C++

Beast is a C++ header-only library serving as a foundation for writing interoperable networking libraries by providing low-level HTTP/1, WebSocket, and networking protocol vocabulary types and algorithms using the consistent asynchronous model of Boost.Asio. Symmetry: Algorithms are role-agnostic; build clients, servers, or both.

arduinoWebSockets - arduinoWebSockets

  •    C++

a WebSocket Server and Client for Arduino based on RFC6455. version 2.0 and up is not compatible with AVR/ATmega, check ATmega branch.

ws - Tiny WebSocket library for Go.

  •    Go

RFC6455 WebSocket implementation in Go. GoDoc.

einaros-ws

  •    Javascript

`ws` is a simple to use, blazing fast and thoroughly tested websocket client, server and console for node.js, up-to-date against RFC-6455