/devtools/browser/*
GET/devtools/browser/*
Connect to an already-running Chromium process with a library like puppeteer, or others, that work over chrome-devtools-protocol. Chromium must already be launched in order to not return a 404.
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.