Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DevTools inspector frontend #14

Closed
o0101 opened this issue Nov 28, 2019 · 2 comments
Closed

DevTools inspector frontend #14

o0101 opened this issue Nov 28, 2019 · 2 comments
Labels
new idea Place for new ideas

Comments

@o0101
Copy link
Collaborator

o0101 commented Nov 28, 2019

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.

@o0101 o0101 added the new idea Place for new ideas label Nov 28, 2019
@o0101
Copy link
Collaborator Author

o0101 commented Dec 15, 2019

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

@o0101
Copy link
Collaborator Author

o0101 commented Dec 20, 2019

Solution, Just visit http://localhost:5002 in your normal browser from the same machine you run this on.

@o0101 o0101 closed this as completed Dec 20, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
new idea Place for new ideas
Projects
None yet
Development

No branches or pull requests

1 participant