wstcp | WebSocket to TCP proxy written in Rust | Proxy library

by sile Rust Version: 0.2.0 License: MIT

X-Ray Key Features Code Snippets Community Discussions(1)Vulnerabilities Install Support

kandi X-RAY | wstcp Summary

wstcp is a Rust library typically used in Networking, Proxy applications. wstcp has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. You can download it from GitHub.

[License: MIT] WebSocket to TCP proxy written in Rust.

Support

Quality

Security

License

Reuse

Support

wstcp has a low active ecosystem.

It has 31 star(s) with 6 fork(s). There are 3 watchers for this library.

It had no major release in the last 12 months.

There are 2 open issues and 1 have been closed. On average issues are closed in 5 days. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of wstcp is 0.2.0

Quality

wstcp has 0 bugs and 0 code smells.

Security

wstcp has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

wstcp code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

wstcp is licensed under the MIT License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

wstcp releases are available to install and integrate.

Installation instructions, 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 wstcp

Get all kandi verified functions for this library.

wstcp Key Features

No Key Features are available at this moment for wstcp.

wstcp Examples and Code Snippets

No Code Snippets are available at this moment for wstcp.

Community Discussions

Trending Discussions on wstcp

Reactor Netty websocket channel closed prematurely

QUESTION

Reactor Netty websocket channel closed prematurely

Asked 2021-Aug-18 at 07:11

I have a long running websocket client implemented in java Spring reactor with Netty (spring-boot-starter-parent 2.5.3) targeting Binance ws api. According to specs, the weboscket channel is kept open 24 hours.

The websocket is unexpectedly and prematurely closed after around 3 minutes :

...

ANSWER

Answered 2021-Aug-18 at 07:11

I finally managed to find the root cause.

The underlying error was java websocket 1006 Unexpected Status of SSLEngineResult after an unwrap() operation

After some investigation, I got the returned code 1006 meaning the connection was closed abnormally by the client as documented in the rfc https://datatracker.ietf.org/doc/html/rfc6455#section-7.4.1

1006 is a reserved value and MUST NOT be set as a status code in a Close control frame by an endpoint. It is designated for use in applications expecting a status code to indicate that the connection was closed abnormally, e.g., without sending or receiving a Close control frame.

At that time, I switched from WIFI connection to LAN connection and the issue vanished immediately. My WIFI router was not able to handle the huge payload correctly.

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

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

Vulnerabilities

No vulnerabilities reported

Install wstcp

A precompiled binary for Linux environment is available in the [releases] page.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: