/devtools/page/*
GET/devtools/page/*
Connect to an existing page in Chromium with a library like chrome-remote-interface or others that work the page websocketDebugger URL. You can get this unique URL by calling the /json/list API or by finding the page's unique ID from your library of choice.
Request
Responses
- 101
- 400
- 401
- 403
- 404
- 408
- 429
- 500
- 503
Indicates successful WebSocket upgrade.
The request contains errors or didn't properly encode content.
The request is missing, or contains bad, authorization credentials.
The request targets a destination that is not allowed.
Resource couldn't be found.
The request took has taken too long to process.
Too many requests are currently being processed.
An internal error occurred when handling the request.
Service is unavailable.