Replies: 2 comments 7 replies
-
As it looks that the ex handler kicked in, it sounds a bit like incomplete configuration. Please post/attach your RB's config. |
Beta Was this translation helpful? Give feedback.
7 replies
-
@MarcinOrlowski I can confirm that this issue still persist. I did as comments in response_builder.php suggested => HttpException::class => [
// used by unauthenticated() to obtain api and http code for the exception
HttpResponse::HTTP_UNAUTHORIZED => [
'api_code' => ApiCodes::UNAUTHORIZED,
'http_code' => HttpResponse::HTTP_UNAUTHORIZED,
],
] However, no matter what I do, HTTP response code is always 500. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello, could you please help me.
I have implemented
ExceptionHandlerHelper
inside\App\Exceptions\Handler::render
and it works well.When I try to access a wrong route or manually abort execution using
abort(404);
I receive a response which I was expected, example:
But the http code is always
500
, how can I make it automatically set404
code when it is needed? The Laravel itself does it correctly.Beta Was this translation helpful? Give feedback.
All reactions