fruitcake / laravel-cors

Adds CORS (Cross-Origin Resource Sharing) headers support in your Laravel application


CORS Middleware for Laravel

Software License
Build Status
Total Downloads

Based on


The laravel-cors package allows you to send Cross-Origin Resource Sharing
headers with Laravel middleware configuration.

If you want to have a global overview of CORS workflow, you can browse
this image.

Upgrading from 0.x

When upgrading from 0.x versions, there are some breaking changes:

  • The vendor name has changed (see installation/usage)
  • Group middleware is no longer supported.
  • A new 'paths' property is used to enable/disable CORS on certain routes. This is empty by default!
  • The casing on the props in cors.php has changed from camelCase to snake_case, so if you already have a cors.php file you will need to update the props in there to match the new casing.


  • Handles CORS pre-flight OPTIONS requests
  • Adds CORS headers to your responses
  • Match routes to only add CORS to certain Requests


Require the fruitcake/laravel-cors package in your composer.json and update your dependencies:

composer require fruitcake/laravel-cors

Global usage

To allow CORS for all your routes, add the HandleCors middleware in the $middleware property of app/Http/Kernel.php class:

protected $middleware = [
    // ...

Now update the config to define the paths you want to run the CORS service on, (see Configuration below):

'paths' => ['api/*'],


The defaults are set in config/cors.php. Publish the config to copy the file to your own config:

php artisan vendor:publish --tag="cors"

Note: When using custom headers, like X-Auth-Token or X-Requested-With, you must set the allowed_headers to include those headers. You can also set it to ['*'] to allow all custom headers.

Note: If you are explicitly whitelisting headers, you must include Origin or requests will fail to be recognized as CORS.


return [

     * You can enable CORS for 1 or multiple paths.
     * Example: ['api/*']
    'paths' => [],

    * Matches the request method. `[*]` allows all methods.
    'allowed_methods' => ['*'],

     * Matches the request origin. `[*]` allows all origins.
    'allowed_origins' => ['*'],

     * Matches the request origin with, similar to `Request::is()`
    'allowed_origins_patterns' => [],

     * Sets the Access-Control-Allow-Headers response header. `[*]` allows all headers.
    'allowed_headers' => ['*'],

     * Sets the Access-Control-Expose-Headers response header.
    'exposed_headers' => false,

     * Sets the Access-Control-Max-Age response header.
    'max_age' => false,

     * Sets the Access-Control-Allow-Credentials header.
    'supports_credentials' => false,

allowed_origins, allowed_headers and allowed_methods can be set to ['*'] to accept any value.

Note: Try to be a specific as possible. You can start developing with loose constraints, but it's better to be as strict as possible!

Note: Because of http method overriding in Laravel, allowing POST methods will also enable the API users to perform PUT and DELETE requests as well.


On Lumen, just register the ServiceProvider manually in your bootstrap/app.php file:


Also copy the cors.php config file to config/cors.php and put it into action:


Global usage for Lumen

To allow CORS for all your routes, add the HandleCors middleware to the global middleware and set the paths property in the config.

    // ...

Disabling CSRF protection for your API

If possible, use a different route group with CSRF protection enabled.
Otherwise you can disable CSRF for certain requests in App\Http\Middleware\VerifyCsrfToken:

protected $except = [


Released under the MIT License, see LICENSE.