Note that there are some explanatory texts on larger screens.

plurals
  1. USWilliam Scalf
    primarykey
    data
    text
    plurals
    1. This table or related slice is empty.
    1. COThat...does indeed work! When I looked at this with fresh eyes this morning, I ended up going a different route, but I'm marking as answer because it succinctly addresses the problem as presented. Thanks!
      singulars
    2. COWell, yeah - my intention is for as much information as possible to be captured on the server, and a minimal response to be sent to the client. The problem is that, for most errors, we use built-in mechanisms in the framework to capture fault details for logging (MVC and HTTP IExceptionFilters and the Application_Error event), and that's all well and good, but there appears to be a category of errors inside and around web api where no such mechanism exists - or, at least, not that I can find.
      singulars
    3. COI might be misunderstanding it, but from how I'm reading it, the only way to get an exception object that I can log would be to follow the hack mentioned at the end of my question - to enable including error detail in all responses, then parsing that error detail on error to attempt to reconstruct the exception that was originally thrown, then manually scrub those details from the response before sending it to the client. ..And while that should work, it sounds crude, brittle, and prone to losing diagnostic information and/or unintentionally leaking that information to clients.
      singulars
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload