Debugging HTTP Requests in ASP.NET Core Across Environments

When the same HTTP request works in dev but fails in production, debugging gets messy fast. Example: a request returns 200 in dev but 400 in prod because of a missing header or slightly different payload—and it’s not obvious why. Most of the time, this means jumping between logs, Postman, and custom middleware, trying to spot the difference. To simplify this, I started working on a lightweight way to capture and inspect HTTP requests and responses directly inside the app (headers, body, timing).