PHPackages                             offline/oc-cors-plugin - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. offline/oc-cors-plugin

ActiveOctober-plugin

offline/oc-cors-plugin
======================

Setup and manage Cross-Origin Resource Sharing headers in October CMS

v1.1.1(2y ago)122028MITPHP

Since Feb 12Pushed 2y ago2 watchersCompare

[ Source](https://github.com/OFFLINE-GmbH/oc-cors-plugin)[ Packagist](https://packagist.org/packages/offline/oc-cors-plugin)[ RSS](/packages/offline-oc-cors-plugin/feed)WikiDiscussions develop Synced 1mo ago

READMEChangelog (2)DependenciesVersions (8)Used By (0)

CORS plugin for October CMS
===========================

[](#cors-plugin-for-october-cms)

This plugin is based on [https://github.com/barryvdh/laravel-cors](https://github.com/barryvdh/laravel-cors/blob/master/config/cors.php).

All configuration for the plugin can be done via the backend settings.

The following cors headers are supported:

- Access-Control-Allow-Origin
- Access-Control-Allow-Headers
- Access-Control-Allow-Methods
- Access-Control-Allow-Credentials
- Access-Control-Expose-Headers
- Access-Control-Max-Age

Currently these headers are sent for every request. There is no per-route configuration possible at this time.

Setup
-----

[](#setup)

After installing the plugin visit the CORS settings page in your October CMS backend settings.

You can add `*` as an entry to `Allowed origins`, `Allowed headers` and `Allowed methods` to allow any kind of CORS request from everywhere.

It is advised to be more explicit about these settings. You can add values for each header via the repeater fields.

> It is important to set these intial settings once for the plugin to work as excpected!

### Filesystem configuration

[](#filesystem-configuration)

As an alternative to the backend settings you can create a `config/config.php` file in the plugins root directory to configure it.

The filesystem configuration will overwrite any defined backend setting.

```