-
-
Notifications
You must be signed in to change notification settings - Fork 83
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WebSocket traffic interception support #121
Comments
@ferenc-a, what is your use case? Curious which approach may be more useful. |
I'd like to parse the messages, modify them, and conditionally inject more inbetween them. |
Ok, just pushed a commit for this. Would this work for your purposes? Can you try it out? |
I'm going on vacation soon, so it might be more than a week until I can try it sorry. |
It's possible to intercept the HTTP to WebSocket upgrade message (#27 (comment)), but not the traffic afterwards. It would be nice to have the functionality (like for example, here: https://github.com/joeferner/node-http-mitm-proxy/tree/master?tab=readme-ov-file#proxy_onWebSocketConnection).
If full support would take too much, at least the WebSocket made by the library should be exposed, or there should be another callback that is provided to library users where they can access it momentarily, before it's fully initialized.
The text was updated successfully, but these errors were encountered: