Field kit · camofox-browser 1.5.2

Investigate Camofox

What this browser leaks, and what Camoufox rewrites in C++ before a page script runs.

01This browser

The read stays local. Nothing is uploaded.

Camoufox UA

  • Waiting for the read.

    Host candidates can leak a local address. Run this only if you want that counted here. The address itself is not shown or stored.

    02How a session is built

    One Express server, one Camoufox process, isolated contexts.

    1. Server Express holds the browser. Tabs, snapshots, and input go through the REST API.
    2. Session Each userId gets a browser context. Cookies and storage do not cross users.
    3. Tabs A sessionKey groups tabs. Interactive nodes get refs such as e1 and e2. Refs reset on navigation, and a stale ref returns HTTP 422.
    4. Idle A quiet context expires. The browser shuts down after about five minutes and launches again on the next request.

    Proxies are round-robin or sticky backconnect. A Google block rotates the context, up to three tries. Snapshots are the accessibility tree, about a tenth the size of the raw HTML.

    CAMOFOX_PORT
    9377
    MAX_SESSIONS
    50
    MAX_TABS_PER_SESSION
    10
    SESSION_TIMEOUT_MS
    600000
    BROWSER_IDLE_TIMEOUT_MS
    300000
    PROXY_STRATEGY
    round_robin

    03REST surface

      04Scratch pad

      Stored in localStorage on this browser. Not uploaded.