Hi, We built Gouger after many years of troubleshooting enterprise web apps, where the same question kept coming back: why did the session break? A login loops back to the sign-in page, a call suddenly returns 403, a page hangs for 30 seconds. The answer is almost always in the HTTP traffic, but finding it in a capture of a few thousand requests takes hours, even with Fiddler or the browser's developer tools. Gouger is a debugging proxy that also reads the traffic for you. Click one button and it captures everything your browser does, HTTPS included. Then 34 built-in checks point at what went wrong, each with a hint for the fix: Single sign-on: redirect loops, failed or replayed tickets, resources bounced to the login page Cookies and sessions: dropped, shadowed or insecure cookies Timing: slow backends, failing responses, load-balancer flips between servers You can also open a HAR file someone sent you and get the same diagnosis offline. When you need to pass it on, export a report with cookies, tokens and credentials redacted. It runs locally, and captured traffic never leaves your computer. It's free for Windows and Linux, macOS is in preparation. I'd love your feedback, especially on this: what failure have you chased through HTTP traffic that Gouger should catch? Thanks!

Gouger

Web debugging proxy that tells you what broke

Web debugging proxy that tells you what broke