Part of HTTP Toolkit: powerful tools for building, testing & debugging HTTP(S), WebRTC, and more
This is an example web extension you can use as a base to build your own WebRTC-intercepting web extensions for debugging.
This is a proof-of-concept example to start from, not something you'd immediately use out of the box. To intercept WebRTC using this repo:
- Clone this repo
npm install- Modify the logic in background.ts to configure MockRTC however you'd like
- Launch the extension
- You may be able to run
npm startto launch a MockRTC backend, build the code in this repo into a usable web extension, and open a new Chrome window with that extension temporarily installed. - Or this may fail, if you don't have Chrome in your PATH as
google-chrome, if you're using Windows, if Chrome is already running, or probably in various other cases. - As an alternative, you can run
npm run start:backend, and then install the extension manually in any Chromium-based browser by going tochrome://extensions/, enabling developer mode, clicking 'Load unpacked' and then selecting thepublicfolder in this repo on your machine. - Should also work in Safari & Firefox and anywhere else supporting web extensions, although I haven't tested.
- You may be able to run
- Test it on the official samples at https://webrtc.github.io/samples/, for example:
- Go to
chrome://extensionsand click the 'service worker' link on the MockRTC extension open the console for your extension. - Open https://webrtc.github.io/samples/src/content/datachannel/messaging/ for a convenient chat demo.
- Click connect, which will open two MockRTC connections in that one page, connected together.
- Send a message in either direction - you'll see 'Sent: X' & 'Received: X' (from the two connections) appear in your extension console.
- Go to
Once you've got the basics working, you can extend the code in background.ts to monitor any WebRTC events or define any rules you'd like to do anything you're interested in. If you run into limitations in MockRTC and there's more capabilities you need there, please open an issue.
This project has received funding from the European Union’s Horizon 2020 research and innovation programme within the framework of the NGI-POINTER Project funded under grant agreement No 871528.
