C#•3y ago

Processing of the HTTP request resulted in an exception. Please see the HTTP response returned by...

Hello, I am working on an API in MVC and I want throw an exception, but I get the following error:

Processing of the HTTP request resulted in an exception. Please see the HTTP response returned by the 'Response' property of this exception for details.

Processing of the HTTP request resulted in an exception. Please see the HTTP response returned by the 'Response' property of this exception for details.

I don't know what to do, I looked everywhere on the internet and nothing, here is my code for executing an error:

var resp = new HttpResponseMessage(HttpStatusCode.NotFound)
                {
                    Content = new StringContent(JsonConvert.SerializeObject("Code has been not found"), Encoding.UTF8, "application/json"),
                    ReasonPhrase = "Code Not Found",
                };
throw new HttpResponseException(resp);

var resp = new HttpResponseMessage(HttpStatusCode.NotFound)
                {
                    Content = new StringContent(JsonConvert.SerializeObject("Code has been not found"), Encoding.UTF8, "application/json"),
                    ReasonPhrase = "Code Not Found",
                };
throw new HttpResponseException(resp);

var resp = new HttpResponseMessage(HttpStatusCode.NotFound)
                {
                    Content = new StringContent(JsonConvert.SerializeObject("Code has been not found"), Encoding.UTF8, "application/json"),
                    ReasonPhrase = "Code Not Found",
                };
throw new HttpResponseException(resp);

var resp = new HttpResponseMessage(HttpStatusCode.NotFound)
                {
                    Content = new StringContent(JsonConvert.SerializeObject("Code has been not found"), Encoding.UTF8, "application/json"),
                    ReasonPhrase = "Code Not Found",
                };
throw new HttpResponseException(resp);

Joao•2/20/23, 8:47 AM

@HAHOOS your application is probably not handling the exception thrown in the controller. Is there a specific benefit to throw an exception in the example given?

You could, as alternative return an HttpNotFoundResult:

return new HttpNotFoundResult("optional description");

return new HttpNotFoundResult("optional description");

Or in .NET latest versions return

ProblemDetails

ProblemDetails

or a

NotFound

NotFound

objects.

JJoao @HAHOOS your application is probably not handling the exception thrown in the co...

HAHOOSOP•2/20/23, 8:54 AM

Sadly, I can't return a result, because as an output I got a custom object called

Pending

Pending

JJoao @HAHOOS your application is probably not handling the exception thrown in the co...

HAHOOSOP•2/20/23, 8:55 AM

A benefit for throwing an exception in the example is to notify the user/code that there was no code found in the database

FusedQyou•2/20/23, 9:03 AM

You don't throw exceptions for that

FusedQyou•2/20/23, 9:03 AM

Exceptions are for errors, not stuff that can happen when using the program like it's supposed to be used

FusedQyou•2/20/23, 9:03 AM

Not finding a resource is not an error

FusedQyou•2/20/23, 9:03 AM

I assume your code is now returning a NotFound embedded inside an InternalServerError, which is not how it's supposed to be

FusedQyou•2/20/23, 9:05 AM

If you properly implement "negative" responses, their code all start with a 4 or 5 (NotFound is 404, InternalServerError is 500). 5 usually means an error, and 4 means a negative response that can happen when using the application like normal.

Joao•2/20/23, 9:05 AM

In my humble opinion the application should not return the object

Pending

Pending

because that resource does not exist in the case of a 404 HTTP response code. This is something you could consider while designing your application.

If you want to stick to the exception you need to make sure your application handles it, see this example: https://learn.microsoft.com/en-us/aspnet/web-api/overview/error-handling/exception-handling

Exception Handling in ASP.NET Web API - ASP.NET 4.x

Describes ASP.NET Web API executes error and exception handling and provides examples for errors and exceptions.

FusedQyou•2/20/23, 9:05 AM

Pretty sure if you properly return a response like a 404, you can find some

isPositiveResponse

isPositiveResponse

parameter you can check. Then just check if the code is a 404, or return an error otherwise.

FusedQyou•2/20/23, 9:06 AM

Or maybe not, this is MVC after all, and I would not be surprised if their whole structure is different

HAHOOSOP•2/20/23, 10:50 AM

I got it working, but I want it shorter so it will only display

message

message

and

code

code

. My current response:

{
  "version": "1.1",
  "content": {
    "headers": [
      {
        "key": "Content-Type",
        "value": [
          "application/json; charset=utf-8"
        ]
      }
    ]
  },
  "statusCode": 404,
  "reasonPhrase": "Code Not Found",
  "headers": [],
  "trailingHeaders": [],
  "requestMessage": null,
  "isSuccessStatusCode": false
}

{
  "version": "1.1",
  "content": {
    "headers": [
      {
        "key": "Content-Type",
        "value": [
          "application/json; charset=utf-8"
        ]
      }
    ]
  },
  "statusCode": 404,
  "reasonPhrase": "Code Not Found",
  "headers": [],
  "trailingHeaders": [],
  "requestMessage": null,
  "isSuccessStatusCode": false
}

HAHOOSOP•2/20/23, 10:51 AM

It now outputs

HttpResponseMessage

HttpResponseMessage

and the code is:

var resp = new HttpResponseMessage(HttpStatusCode.NotFound)
                {
                    Content = new StringContent(JsonConvert.SerializeObject("Code has been not found"), Encoding.UTF8, "application/json"),
                    ReasonPhrase = "Code Not Found",
                };
                return resp;

var resp = new HttpResponseMessage(HttpStatusCode.NotFound)
                {
                    Content = new StringContent(JsonConvert.SerializeObject("Code has been not found"), Encoding.UTF8, "application/json"),
                    ReasonPhrase = "Code Not Found",
                };
                return resp;

HHAHOOS I got it working, but I want it shorter so it will only display `message` and `c...

FusedQyou•2/20/23, 11:01 AM

Well you can adjust the response using a middleware, but I can tell you out of experience that modifying a stream to output a custom response is very shit to work with. It works, but it's going to require A LOT of code

FusedQyou•2/20/23, 11:02 AM

That said, this response if very informative. I understand it's of no use to you, but this is how a proper response should look like, and the only benefit of making it shorter is only because you don't need it currently.

Accord•2/21/23, 11:26 AM

Was this issue resolved? If so, run

/close

/close

otherwise I will mark this as stale and this post will be archived until there is new activity.

{ "version": "1.1", "content": { "headers": [ { "key": "Content-Type", "value": [ "application/json; charset=utf-8" ] } ] }, "statusCode": 404, "reasonPhrase": "Code Not Found", "headers": [], "trailingHeaders": [], "requestMessage": null, "isSuccessStatusCode": false }

var resp = new HttpResponseMessage(HttpStatusCode.NotFound) { Content = new StringContent(JsonConvert.SerializeObject("Code has been not found"), Encoding.UTF8, "application/json"), ReasonPhrase = "Code Not Found", }; return resp;

Processing of the HTTP request resulted in an exception. Please see the HTTP response returned by...

Similar Threads

Similar Threads

Similar Threads