500 and 405 ASP.NET Core responses lose response body

[georgidhristov]

Description

Unhandled exceptions currently produce empty response bodies inside DebugProbe.

The request entry correctly shows:

• status code 500
• request metadata

But the actual exception response body and stack trace are missing.

Expected

When an exception occurs, DebugProbe should capture and display:

• exception message
• stack trace
• generated error response body

Actual

Response body is stored as empty even though ASP.NET Core generates and returns an exception response to the client.

Swagger / Browser Response

DebugProbe

Notes

The issue was initially observed with unhandled exception responses (500), but it also appears with certain framework-generated responses such as 405 Method Not Allowed.

Normal application responses continue to work correctly.

Reproduction

Create endpoint throwing exception:

throw new Exception("Database failure");

Impact

This is a major limitation for a debugging tool because 500 responses are one of the most important scenarios developers need to inspect.