chroxy v0.7.0 API Reference

Provides Chrome Remote Debug Protocol connections.

Provides connections to Browser instances, through the orchestration of proxied connections to processes managing the OS browser processes.

Process which establishes a single proxied websocket connection to an underlying chrome browser page remote debugging websocket.

GenServer process which manages a port connection to a Chrome browser OS Process as well as a ChromeRemoteInterface.Session to the browser instance providing command and control over the instance.

DynamicSupervisor for Chroxy.ChromeServer

Reponsible for accepting upstream connections from client, and delegating ownership of the connection to a new Chroxy.ProxyServer process which will in turn create the transparent forwarding channel to the downstream host.

Maps connection metadata (such as page_id in case of Chrome) in order to route incoming request to the correct browser process. Will monitor browser processes and automatically remove regsitrations if a browser process dies during the course of operation.

Transparent Proxy Server manages the relay of communications between and upstream and downstream tcp connections. Support customer extensions through callbacks of Hook modules which implement the Chroxy.ProxyServer.Hook behaviour.

Behaviour for Proxy Server Hooks. Example: Chroxy.ChromeProxy