Temporarily disable / bypass Middleware

Question

In my Application I implemented a OAuth2-Server (oauth2-server-laravel) in combination with a custom Authentication Package (Sentinel by Cartalyst).

In my routes.php:

Route::group(['before' => 'oauth'], function()
{
    // ... some routes here
}

So the request must provide an authorization header or the application quits with an OAuthException.

Now I want to unittest my controllers. So I have to seed my database with a OAuth session and access token for every test. Then overwrite the call()-method of TestCase and set the HTTP-Authorization Header with the Bearer Token.

Is there a way to disable or bypass middleware (in my case just for unit testing)?

In Laravel 4 they were called route filters and they were disabled in the testing environment anyway. You could also manually enable/disable them with Route::enableFilters().

I would also like to know the answer to this, my reading so far is that it's not possible to disable middleware in Laravel 5 the way that route filters were disabled in testing mode in Laravel 4. However I'm keen to be proven wrong. — delatbabel, Apr 07 '15 at 10:13

score 7 · Accepted Answer · answered Jun 10 '15 at 08:35

7

Apparently with the release of Laravel 5.1 yesterday a disableMiddleware() method was added to the TestCase class, which now does exactly what I wanted.

Problem solved. :)

answered Jun 10 '15 at 08:35

rookian

1,045
14
38

3

So just put `use WithoutMiddleware;` in your test case class – tread Dec 18 '15 at 16:16
1

An improvement on this has been merged to framework that allows to disable a specific set of middlewares. see https://github.com/laravel/framework/pull/18673 – meysam Apr 28 '17 at 09:48

score 2 · Answer 2 · answered Apr 07 '15 at 11:01

The only answer that I could come up with was to put a bypass in the actual middleware itself. For example:

public function handle($request, Closure $next)
{
    // Don't validate authentication when testing.
    if (env('APP_ENV') === 'testing') {
        return $next($request);
    }
    // ... continue on to process the request
}

I don't like the idea of making the middleware dependent on the app environment but I couldn't see any other options.

Moon · Answer 3 · 2015-04-17T04:27:02.153

0

Here's a package that I worked on after having the same issue.

https://github.com/moon0326/FakeMiddleware

edited Apr 17 '15 at 04:27

answered Apr 16 '15 at 23:55

Moon

22,195
68
188
269

Temporarily disable / bypass Middleware

3 Answers3

Linked