Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Help test the raw TCP wireless backend

See original GitHub issue

Direct Sockets API (formerly, “raw sockets API”) (Chrome Platform Status) allows Web applications to create raw TCP or UDP sockets .

It has been implemented in Chrome for quite a while, but because the uncertainty and unsolved problems in the spec, it never been enabled.

To enable Direct Sockets API in a Chromium-based browser:

Chromium before 98: add --enable-features=DirectSockets command line arguments.
Chromium 98 and after: also add --restricted-api-origins=https://www.example.com to command line arguments, or set allowed origins from chrome://flags/#restricted-api-origins. (replace https://www.example.com with real origin using the Direct Sockets API, to add multiple origins, separates them with comma)

It should be possible to create an ADB backend using this API to achieve plugin-free wireless connection.

Issue Analytics

State:
Created 2 years ago
Comments:7 (5 by maintainers)

Top GitHub Comments

1reaction

ziyunfeicommented, Jul 30, 2022

Just FYI: restricted-api-origins has been renamed to isolated-app-origins.

https://github.com/chromium/chromium/commit/8a471ec271ef4d84e7ebc79c504f8d036178880c

0reactions

yume-chancommented, Mar 31, 2022

The new steps only apply to Chrome Dev/Canary/Chromium versions after March 15th. I don’t know if any Stable/Beta versions are shipped with this change. So also try the old steps.

In fact, all versions released between Feb 15th and Marth 15th have DirectSockets feature disabled (by mistake). Stable/Beta are most possible in this range.

If you are using Microsoft Edge Dev/Canary, the code sometimes lags behind Chromium for about 10 days. So it is even harder to guess.