Proxer is a desktop HTTP and HTTPS interception proxy built with Tauri v2 and a Next.js UI. It captures traffic into a local SQLite database, shows it in a real-time History view, and builds a Sitemap from observed endpoints.

• HTTP and HTTPS proxy with CONNECT support
• Optional TLS interception for HTTPS visibility
• HTTP History with request and response details
• Sitemap view that groups traffic by host and endpoint
• Request interception with scope gating
• Built-in tools: Repeater, Intruder, Scanner, Decoder, Comparer, Logger, and Extensions
• Sessions and projects: temporary session or project on disk (choose a folder on startup)
• Light and dark themes with color and grayscale variants
• Windows system proxy toggle with automatic restore on stop
• Local persistence via SQLite per project

Main navigation is:

• Dashboard
• HTTP History
• Sitemap
• Intercept
• Proxy

1. The proxy listens on a local address, usually 127.0.0.1:8080.
2. For HTTP requests, the proxy can capture full request and response data.
3. For HTTPS requests, the browser first creates a CONNECT tunnel. You can capture the tunnel destination without decrypting it.
4. If you enable TLS interception and install the generated CA certificate, Proxer can decrypt HTTPS traffic and capture full request and response data.
5. Captured traffic is stored in a local SQLite database and drives the Dashboard, History, and Sitemap views.

Prebuilt installers and archives are provided in GitHub Releases.

1. Download the latest release for your operating system.
2. Install or extract it.
3. Launch Proxer.

This repository includes a GitHub Actions workflow that builds releases for Windows, macOS, and Linux.

• Push a git tag like v0.1.0 to trigger a draft GitHub Release with the build artifacts attached.
• Publish the draft release once you have verified the artifacts.

To capture traffic, configure your browser to use the Proxer proxy listener.

• Host: 127.0.0.1
• Port: 8080, or the port you configured in the Proxy view

To see HTTPS request and response contents:

1. Open Proxy.
2. Enable SSL Interception.
3. Export the CA certificate.
4. Install the CA certificate in your browser or operating system trust store.

If you do not install the CA, HTTPS traffic will typically appear as CONNECT tunnels only.

Proxer uses:

• Node.js and npm for the Next.js frontend
• Rust toolchain for the Tauri backend

• Node.js 18 or newer
• Rust stable toolchain
• Tauri v2 prerequisites for your platform

Platform notes:

• Windows: Microsoft C++ Build Tools and WebView2
• macOS: Xcode Command Line Tools
• Linux: required system libraries for Tauri and WebKit based webviews, depending on your distribution

From the repository root:

1. Install frontend dependencies:
   • cd frontend
   • npm install
2. Build and run via Tauri:
   • cd ..\src-tauri on Windows, or cd ../src-tauri on macOS and Linux

From src-tauri:

• cargo tauri dev

This starts the Next.js dev server and launches the Tauri app window.

From src-tauri:

• cargo tauri build

This builds the frontend, exports it to frontend/out, and builds a native app.

You can also build from the repository root using the helper scripts:

• Windows: scripts\\build-windows.bat
• macOS and Linux: scripts/build-unix.sh

On Windows, the build produces:

• A portable app executable at src-tauri/target/release/proxer.exe
• An installer executable at src-tauri/target/release/bundle/nsis/

If you only want the portable executable and you do not want an installer:

• cargo tauri build --no-bundle

On macOS, the build produces a DMG under src-tauri/target/release/bundle/dmg/ and an app bundle under src-tauri/target/release/bundle/macos/.

On Linux, the build produces:

• An AppImage under src-tauri/target/release/bundle/appimage/
• A Debian package under src-tauri/target/release/bundle/deb/

cargo tauri build builds for the operating system you run it on. To produce Windows, macOS, and Linux artifacts, you must build on each OS, or use CI with a matrix that builds on Windows, macOS, and Linux.

Captured traffic is stored locally. Do not use Proxer on networks or targets that you do not own or have explicit permission to test.

• frontend/ Next.js UI
• src-tauri/ Tauri backend, proxy engine, and storage

• This is expected for HTTPS without TLS interception and CA installation.
• Enable SSL Interception in the Proxy view and install the exported CA certificate.

• If Intercept is enabled and the system proxy routes traffic through Proxer, other apps can pause waiting for you to forward or drop. Use system proxy only when you want to intercept traffic from desktop apps. Browsers can be captured by setting a browser proxy without enabling the system proxy.

• Temporary sessions use a database under your OS temp directory.
• Projects on disk use the folder you picked at startup, with a proxer.db inside it.