Added support for proxying websockets through the victim browser #77
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.
Currently, websockets connections are not proxied through the victim's extension and are handled by the CursedChrome server. The MR implements several new RPC methods to fix this.
Changes:
onWebSocketConnection
rule to AnyProxy to allow manipulation of WebSocket traffic.onWebSocketConnection
rule and added 2 new RPC methods:WS_MESSAGE
andWS_CLOSE
.WS_CONNECT
,WS_MESSAGE
andWS_CLOSE
.