The Chromium team has rolled out a permission called Local Network Access (LNA) that was just applied to WebSocketd in Chrome 147. With this, apps hosted on remote hosts can't access local network services (including localhost) without an extra permission.
I created an issue on the upstream project (obsproject/obs-websocket/issues/1340), as I believe some additional support from the WS server itself will be needed. The migration docs suggest making a simple fetch request to trigger the permission prompt. But, I haven't been able to find such an endpoint that doesn't require the WS upgrade and has CORS support.
Once in place though, it would be nice if this library could detect the case and handle the permission request at connection. So, making this issue to both raise awareness and to track potential future work.
The Chromium team has rolled out a permission called Local Network Access (LNA) that was just applied to WebSocketd in Chrome 147. With this, apps hosted on remote hosts can't access local network services (including localhost) without an extra permission.
I created an issue on the upstream project (obsproject/obs-websocket/issues/1340), as I believe some additional support from the WS server itself will be needed. The migration docs suggest making a simple
fetchrequest to trigger the permission prompt. But, I haven't been able to find such an endpoint that doesn't require the WS upgrade and has CORS support.Once in place though, it would be nice if this library could detect the case and handle the permission request at connection. So, making this issue to both raise awareness and to track potential future work.