Debugging HTTP Requests in ASP.NET Core Across Environments

Source: Dev.to

Problem

When the same HTTP request works in development but fails in production, debugging can become messy quickly.
A request might return 200 in dev but 400 in prod due to a missing header or a slightly different payload, and the cause isn’t obvious.

Typical Workflow

• Jump between logs, Postman, and custom middleware.
• Manually compare request details across environments.

Proposed Approach

I’m building a lightweight tool to capture and inspect HTTP requests and responses directly inside the app (including headers, body, and timing).
The goal is to capture everything in one place and compare requests across environments to quickly identify differences.

Current Status

• Early stage.
• Exploring better comparison and visualization features.

How Do You Debug These Cases Today?

Feel free to share your strategies and experiences.

Try It Out

• GitHub:
• NuGet: