Feature Request Type
Other
Feature Request Type (Other)
No response
Requested Feature
With the Chromium 147 release, a new LNA (Local Network Access) restriction has been applied to WebSockets (feature doc here). The side effect of this is that deployed web apps that use the OBS WebSocket JS library can no longer connect to OBS running on localhost. For example, the OBS Web project is no longer able to connect.
While the browser is supposed to notice the request to localhost and then give a prompt, I'm not seeing that occur for WebSockets. The reference doc suggests doing a simple fetch against an endpoint to trigger the prompt.
The struggle is that I haven't been able to find an endpoint provided by the OBS WebSocket server that can be used to do this.
My request is to create a simple GET endpoint (such as /health) that fully supports CORS and simply returns back a 200 OK. With this, the JS library could be updated to detect this condition (running non-locally and talking to a local network service), hit the endpoint, get the required permissions, and go from there.
Requested Feature Usage Scenario
Restores the functionality of communicating with the WS server from deployed applications.
Feature Request Type
Other
Feature Request Type (Other)
No response
Requested Feature
With the Chromium 147 release, a new LNA (Local Network Access) restriction has been applied to WebSockets (feature doc here). The side effect of this is that deployed web apps that use the OBS WebSocket JS library can no longer connect to OBS running on localhost. For example, the OBS Web project is no longer able to connect.
While the browser is supposed to notice the request to localhost and then give a prompt, I'm not seeing that occur for WebSockets. The reference doc suggests doing a simple
fetchagainst an endpoint to trigger the prompt.The struggle is that I haven't been able to find an endpoint provided by the OBS WebSocket server that can be used to do this.
My request is to create a simple GET endpoint (such as
/health) that fully supports CORS and simply returns back a 200 OK. With this, the JS library could be updated to detect this condition (running non-locally and talking to a local network service), hit the endpoint, get the required permissions, and go from there.Requested Feature Usage Scenario
Restores the functionality of communicating with the WS server from deployed applications.