[FEATURE] Web Browser Connection Support (Clientless Web Access)

Title

[FEATURE] Web Browser Connection Support (Clientless Web Access)

Platform

N/A

Is it related to an issue?

No.

The Solution

Currently, Termix-SSH does a fantastic job of managing traditional remote sessions. However, a significant portion of modern IT infrastructure (such as firewalls, storage arrays, and networking gear) is managed almost exclusively via web interfaces.

Accessing these interfaces securely usually requires a VPN or spinning up a resource-heavy jump host with a full desktop environment. There is currently no native, lightweight way in Termix-SSH to securely manage, interact with, and audit these web-only administrative sessions.

Additional Context

I propose adding an Agentless "Web Gateway" connection type directly into Termix-SSH. Instead of relying on a containerized headless browser or a VNC jump host, Termix-SSH would act as a modern ZTNA (Zero Trust Network Access) reverse proxy with on-the-fly DOM injection for session recording.

By utilizing an engine like rrweb alongside a reverse proxy (e.g., utilizing Node.js http-proxy-middleware), Termix-SSH could:

1. Proxy the internal web application (HTTP/HTTPS) directly to the user's local browser.
2. Intercept the HTML response and inject the rrweb recording payload into the of the target web application.
3. Record DOM mutations, network requests, and user interactions silently in the background, streaming them back to the Termix-SSH server as lightweight JSON.
4. Replay the session natively inside the Termix-SSH Audit interface using rrweb-player.

A reverse proxy consumes single-digit megabytes of RAM. Termix-SSH could handle hundreds of concurrent web sessions without the massive CPU and memory penalty of spinning up headless browsers for every user.

Because the user interacts with the DOM natively in their own proxied browser, there is zero VNC compression, visual artifacting, or input latency.

Start by mapping the proposed reverse-proxy flow, including Node.js http-proxy-middleware, rrweb recording, and rrweb-player replay. Review how Termix-SSH currently handles connections and its Audit interface before defining the scope. Done should include secure proxied web access, session recording, and native audit replay without a headless browser or VNC host.