WebSocket-Node

WebSocket-Node copied to clipboard

How to do basic authentication [Documentation]

7

Hello, I'm trying to connect to a device that runs a websocket server but it requires a username and password. It's basic auth but ws://user@pw:192.169.10.10 doesn't work... Any suggestions?

sk1tt1sh

TCP closed even before accept() or reject()

2

Scenario: - The server receives a WS request and gives the app the `request` instance. - The app must do some async stuff (DB queries or whatever) so it takes...

ibc

ECONNRESET with version 1.0.10

10

Hi, I'm using websocket 1.0.8 in a project with success, but when I try to upgrade it to 1.0.10 I lose the connection, receiving the following error: [Error: read ECONNRESET]...

gsferreira

Can Connection#send() throw an error?

3

If I call `send()` or `sendUTF()` or `sendBytes()` on an already closed `Connection`, or if sending fails due to connection error, would it throw an error? It is not documented.

ibc

Refactor Cookie-handling code into module or delegate to another NPM module

2

theturtle32

Continuing discussion that started in #158 > IMHO connect() should be the method to "activate" the client, and should be callable just once. I tend to agree with @ibc here,...

theturtle32

Add response statusCode, rejection reason, and other header information to connectionFailed event error objects

5

This one should be really easy to do. In addition to creating the error string "Server responded with a non-101 status..." also add the `response.statusCode` and appropriate headers as an...

fresheneesz

Transfer interruption

3

On our distributed filesystem, written in javascript and working with Websockt-Node, we found a strange problem. At first we thought this bug was very randomly so we couldn't find on...

Lukewa

We're currently using a forked version of a super-old library for handling lists of buffers in node. A new package is available here: https://github.com/rvagg/bl Need to test and see what...

theturtle32

Unable to connect with auth info in url and special characters

1

My connection URL is something like: wss://user:[email protected]/path When I try to connect to this URL using plain WebSocket in the browser it has no issue, but with WebSocketClient I get...

chriscoindeskindices