How to fix Laravel's routing error with HttpException?

Question

Am using zizaco entruest rbac and these are my web routes causing error

Route::group(['prefix' => 'user-management', 'middleware' => ['permission:admin']], function() {

    Route::get('/users', function(){
        return "sds";
    });

});

When i try navigating to

http://localhost:8000/user-management/users

am getting an error

Symfony \ Component \ HttpKernel \ Exception \ HttpException
No message

Where could i be wrong

I have commented all other routes and found this to be the culprit

I have setup my rbac as explained

https://github.com/Zizaco/entrust

without middleware it works am adding the middleware as explained github.com/Zizaco/entrust — Geoff
– Geoff, Commented Sep 21, 2017 at 18:10
Did you add 'role' => \Zizaco\Entrust\Middleware\EntrustRole::class, 'permission' => \Zizaco\Entrust\Middleware\EntrustPermission::class, 'ability' => \Zizaco\Entrust\Middleware\EntrustAbility::class, to routeMiddleware array in app/Http/Kernel.php? — Morteza Rajabi
– Morteza Rajabi, Commented Sep 21, 2017 at 18:15
Personally, I prefer to use github.com/DynamicCodeNinja/RBAC instead of Zizaco to handle Role Base Access Control. It has the same functionalities and no bugs at all. — Morteza Rajabi
– Morteza Rajabi, Commented Sep 21, 2017 at 18:22

Cong Chen · Accepted Answer · 2017-09-29 09:35:27Z

8

You should create a 403.blade.php template view under resources/views/errors directory.
Your application's exception handler do not find the exception status code associated view, so it return the exception directly.

answered Sep 29, 2017 at 9:35

Cong Chen

2,43615 silver badges22 bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

Geoff Over a year ago

thats an amazing idea il try and let you know

Geoff Over a year ago

nopw all errors are caught by the blade, but doesnt solve the actual problem of the error caused by the middleware, Thanks for the insight though helped in another area

Basheer Kharoti · Accepted Answer · 2017-09-29 06:35:22Z

5

+50

You need to put auth middleware as well as it checks permission for an auth user within permission middleware. You can fix it by just putting auth middleware and then try logging in, now you can navigate to users url.

 Route::group(['prefix' => 'user-management', 'middleware' => ['auth', 'permission:admin']], function() {

    Route::get('/users', function(){
       return "sds";
    });

 });

answered Sep 29, 2017 at 6:35

Basheer Kharoti

4,3025 gold badges27 silver badges51 bronze badges

1 Comment

Geoff Over a year ago

Thanks i see where i was going wrng i was using the permission even for unauthenticated users doing it this way solved the problem

E. S. · Accepted Answer · 2017-09-28 09:45:10Z

0

To help you with this we need more information.

Is this the only route in your application?
Did you authenticate the user before trying to access /user-manag... ?
What's inside your app/Http/Kernel.php file? Did you add permission middleware?

Not sure what kind of http code are you receiving (is it a 403? or a 500?).

Things you can do that might help:

Enable debug mode (change your .env (or config/app.php) DEBUG to "true")
Check your laravel.log file (storage/logs/laravel.log)
Install laravel-debugbar. This package can give you better insight about what's happening in your app. https://github.com/barryvdh/laravel-debugbar

answered Sep 28, 2017 at 9:45

E. S.

2,91920 silver badges23 bronze badges

1 Comment

Geoff Over a year ago

there are other routes, but when troubleshooting the problem i did comment on all others and left this one which brings the error

Mark Walet · Accepted Answer · 2017-09-28 23:09:17Z

0

I've looked up the middleware. It says the following:

if ($this->auth->guest() || !$request->user()->can($permissions)) {
    abort(403);
}

This means that it crashes without a message if you aren't authenticated or you cannot do something because you don't have permission.

You could try to dd() something in here before the abort. Just to see if it reaches this. If it does check this page in the Laravel documentation about abort() and custom error pages: https://laravel.com/docs/5.5/errors#http-exceptions

answered Sep 28, 2017 at 23:09

Mark Walet

1,21611 silver badges23 bronze badges

Comments

Zulfiqar Tariq · Accepted Answer · 2017-09-29 10:23:26Z

0

apparently your code looks fine. I guess you are having some problem in your middleware its not allowing you to pass through. you have used permission:admin so i guess you should log in as admin and then it will be working fine.

answered Sep 29, 2017 at 10:23

Zulfiqar Tariq

3943 silver badges14 bronze badges

Collectives™ on Stack Overflow

How to fix Laravel's routing error with HttpException?

5 Answers 5

2 Comments

1 Comment

1 Comment

Comments

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

5 Answers 5

2 Comments

1 Comment

1 Comment

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Related