tgpholly
/
tcp-ws-proxy
1
0
Fork 0
Code Issues 3 Pull Requests Packages Projects Releases 2 Wiki Activity

Compare commits

base: tgpholly:master
Branches Tags
tgpholly:master
tgpholly:tcp
tgpholly:1.0.1
tgpholly:1.0.0
..
compare: tgpholly:1.0.1
Branches Tags
tgpholly:tcp
tgpholly:master
tgpholly:1.0.1
tgpholly:1.0.0

No commits in common. "master" and "1.0.1" have entirely different histories.
master ... 1.0.1

1 changed files with 1 additions and 11 deletions
Show Stats Expand all files Collapse all files

12
README.md
View File

@ -1,13 +1,3 @@
# tcp-ws-proxy
A TCP -> WS -> TCP proxy
<hr>
This was originally made for accessing MariaDB databases over a websocket on a site proxied by Cloudflare.
It seems to work pretty well in my testing so i've made the repo for it public.
# Known issues
- When using it over Cloudflare it *is* possible to create too many websocket connections. See [#2](https://git.eusv.net/tgpholly/tcp-ws-proxy/issues/2).
- The console spam can get pretty bad on the client with multiple connections. This should be resolved once all local client connections share the same pooled websockets.
- There is no handling for if the websocket drops but the sockets on both sides do not. It will not re-establish a connection it will just terminate the TCP connections on both sides. This should be improved.
A TCP -> WS -> TCP proxy