Add HTTP target routes
Categories
(Remote Protocol :: CDP, enhancement, P5)
Tracking
(firefox116 fixed)
| Tracking | Status | |
|---|---|---|
| firefox116 | --- | fixed |
People
(Reporter: canadahonk, Assigned: canadahonk)
References
Details
Attachments
(1 file)
Steps to reproduce:
Add HTTP target routes like /json/new into the CDP implementation. Relevant CDP docs: https://chromedevtools.github.io/devtools-protocol/#get-jsonnewurl
(Happy to work on this myself.)
Actual results:
Currently they just return 404s as they aren't implemented.
Expected results:
Handle the requests to the target routes instead of 404.
| Assignee | ||
Comment 1•3 years ago
|
||
Added support for /json/new, /json/activate/{targetId},
/json/close/{targetId}. Rewrote JSONHandler internals to support
different routes by HTTP method, and prefixed routes which are required
by activate and close due to inlining the targetId into the request url.
This is a work-in-progress as tests are yet to be added, and it might be
better to depend upon already open D166873 to avoid merge conflicts.
Passes linting but looking for code feedback, apologies for any troubles
by major internal changes.
Updated•3 years ago
|
Updated•3 years ago
|
Comment 3•3 years ago
|
||
| bugherder | ||
Description
•