One click to start
Route the whole computer through Gouger with a single button: it trusts its own certificate and sets the system proxy. Click again, or close the app, and everything is back the way it was.
Web session debugger · v0.9.0
See exactly why the web session broke.
Gouger is an HTTP(S) debugging proxy for troubleshooting enterprise web applications. It captures every request your browser makes, then tells you what went wrong: a failed single sign-on handshake, a lost cookie, a missing security context, a backend that stopped answering.
What it does
Login and SSO, explained
Follows the full CAS login handshake across servers and flags redirect loops, bounced resources, replayed or failed tickets, and service URLs that do not match.
Sessions and cookies
Groups traffic by session and tracks every cookie the way the browser does, so dropped, shadowed or insecure cookies stand out.
Security context
Spots web-service calls that lose, malform or switch their security context, and access denials that follow from it.
Timing and backends
A per-request waterfall separates server time from transfer, and load-balancer flips show when a session is served by a different backend.
Replay, compose, pause
Replay a request, edit and resend it, or set breakpoints that hold a request or response so you can change it before it continues.
Safe to share
Export a HAR file or a support report with cookies, tokens and credentials redacted, ready to attach to a ticket.
Works offline
Open HAR files captured elsewhere and get the same diagnosis. Nothing leaves your computer.
How it works
- Start Gouger and click the computer button. Windows asks once to trust Gouger's certificate.
- Reproduce the problem in your browser. Requests appear as they happen, with problems marked in place.
- Read the diagnosis, follow the hints, and export a redacted report if someone else needs to see it.
Download
Version 0.9.0, released October 16, 2026.
Checksums: SHA256SUMS. Windows: unzip and run Gouger.exe. Linux: unpack and run sudo make install, or start usr/local/bin/gouger directly.
Questions
What is a debugging proxy?
An HTTP proxy that sits between your browser and the web: every request and response passes through it, so you can inspect headers, cookies, bodies and timing. Gouger also decrypts HTTPS traffic with its own certificate, which it installs and removes for you.
How is it different from a general proxy or the browser's developer tools?
Those show you the traffic; Gouger also reads it for you. Built-in diagnostics recognize common failures, such as SSO redirect loops, dropped or insecure cookies, lost security context, broken caching, slow or failing backends and load-balancer flips, and explain each one with a hint for the fix.
How is Gouger different from Fiddler?
Fiddler is a mature, general-purpose web debugging proxy: application-agnostic, and built for developers and IT to inspect and manipulate any HTTP(S) traffic. Gouger is narrower and opinionated. It is made for troubleshooting web sessions in enterprise applications, so it ships with built-in monitors and checks that read the capture for you. It follows CAS and SSO logins, tracks cookies and security context per session, and flags known failure patterns with a hint for the fix.
Does it help with CAS and single sign-on problems?
Yes. Gouger follows the CAS login handshake across the login server and the services, and flags redirect loops, resources bounced to the login page, failed or replayed tickets, and service URLs that do not match.
Can I analyze a HAR file someone sent me?
Yes. Open a HAR file exported from any browser and Gouger runs the same diagnosis as on live traffic. You can also export a redacted HAR or a support report with cookies, tokens and credentials removed.
Does my traffic leave my computer?
No. Gouger runs locally; captured traffic stays on your machine unless you export it.
Get in touch
Questions, a trial for your team, or a problem Gouger should catch? Write to us.