Websocket proxy #144
Draft
Websocket proxy #144
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
It's possible I was doing it wrong, but I think this library isn't async which might be the biggest issue if we did want to use this library. Maybe there is a better one that still supports proxies. |
Merge latest change to websocket_proxy
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a rough draft of using the websocket-client to support using proxies for the websocket portion of Bing Chat.
I currently just did this to get my personal solution to work, but it's a groundwork to use that could possibly be merged if there is any interest. There are some glaring issues with my changes, including the fact this new websocket isn't being used in other places that I don't use, but that can be improved if again there is interest.