laravel-5

Release Notes 6
building a web UI and an API within the same application. You may group the session and CSRF
routes into a web group, and perhaps the rate limiter in the api group.
In fact, the default Laravel 5.2 application structure takes exactly this approach. For example, in the
default App\Http\Kernel.php file you will find the following:
1 /**
2 * The application's route middleware groups.
3 *
4 * @var array
5 */
6 protected $middlewareGroups = [
7 'web' => [
8 \App\Http\Middleware\EncryptCookies::class,
9 \Illuminate\Cookie\Middleware\AddQueuedCookiesToResponse::class,
10 \Illuminate\Session\Middleware\StartSession::class,
11 \Illuminate\View\Middleware\ShareErrorsFromSession::class,
12 \App\Http\Middleware\VerifyCsrfToken::class,
13 ],
14
15 'api' => [
16 'throttle:60,1',
17 ],
18 ];
Then, the web group may be assigned to routes like so:
1 Route::group(['middleware' => ['web']], function () {
2 //
3 });
However, keep in mind the web middleware group is already applied to your routes by default since
the RouteServiceProvider includes it in the default middleware group.
Rate Limiting
A new rate limiter middleware is now included with the framework, allowing you to easily limit the
number of requests that a given IP address can make to a route over a specified number of minutes.
For example, to limit a route to 60 requests every minute from a single IP address, you may do the
following: