EYeyevinn
devtools

Mint a remote control link for one page.

Changed on

The caller authenticates as they would for any other endpoint; what comes back is a path anyone can open, so it is handed to a person, not published.

Naming Chromium's target directly does not get around the block's Remote Control switch: the target has to be the page of an HTML source with the switch on, the same page [create_block_link] would hand out for it. The two endpoints are different ways of naming the same page, so they cannot be allowed to disagree about whether it may be opened.

post/api/devtools/targets/{target_id}/link

Request

  • The document declares no server URL.
  • Auth
    none declared

Path parameters

target_idstring required

Chromium target id

Response

A remote control link for this HTML source

expires_in_secondsinteger required

How long the link survives without being used. Each use starts it over.

idstring required

A name for this link that is not the credential.

Safe to show, store and log. It is what DELETE /api/devtools/links/{id} takes, so a link can be revoked without anyone having to keep the key.

pathstring required

Path to open in a browser, relative to this Strom instance.

This one is the credential — everything under it is reachable by whoever holds it, so it is handed to a person, never logged or stored.

warningstring required

What the holder of this link can actually reach, in Strom's words: one of [SCREENCAST_CONTROL_WARNING] (with [SHARED_CONTEXT_WARNING] appended when sources share a browser context) or [REMOTE_CONTROL_WARNING]. A client shows it to the operator before handing the link on.

Changes