You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Because we block external access to debugging port, we need to proxy the websocket through our server, and control access via the cookie.
This involves adding another endpoint to the websocket server which
when accessed with proper credentials
will connect to the websocket for the target to inspect.
In addition we will need to serve the devtools frontend as well, and probably make modifications as a result of using a custom websocket proxy.
The text was updated successfully, but these errors were encountered:
at the same time if you want to run devtools locally from the machine that you're running BrowserView on, you can do that you just have to connect to the normal debugging protocol endpoint in a browser on localhost and use port 5002
Because we block external access to debugging port, we need to proxy the websocket through our server, and control access via the cookie.
This involves adding another endpoint to the websocket server which
when accessed with proper credentials
will connect to the websocket for the target to inspect.
In addition we will need to serve the devtools frontend as well, and probably make modifications as a result of using a custom websocket proxy.
The text was updated successfully, but these errors were encountered: