Releases: jdesrosiers/silex-cors-provider
v1.4.0
This release adds the ability to apply a different set of options to different routes.
v0.5.0
This release adds the ability to apply a different set of options to different routes.
v1.3.0
Added the cors.allowHeaders config. By default, all Access-Control-Request-Headers are allowed. If cors.allowHeaders is set, all headers in Access-Control-Request-Headers must be in cors.allowHeaders or the CORS request will be rejected.
v0.4.0
Added the cors.allowHeaders config. By default, all Access-Control-Request-Headers are allowed. If cors.allowHeaders is set, all headers in Access-Control-Request-Headers must be in cors.allowHeaders or the CORS request will be rejected.
v1.2.1
This fixes a bug introduced in the previous release. Because the OPTIONS route matches everything, it led to non-CORS requests returning 405 Method Not Allowed instead of 404 Not Found for non-existent resources. These requests now respond with 404 Not Found as expected.
v0.3.1
This fixes a bug introduced in the previous release. Because the OPTIONS route matches everything, it led to non-CORS requests returning 405 Method Not Allowed instead of 404 Not Found for non-existent resources. These requests now respond with 404 Not Found as expected.
v1.2.0
In this release I added the cors-enabled service. It is now the preferred way to enable CORS support, but the old way still works like it used to. The main benefit is that it works properly for controller collections and controllers. If you enable CORS support for the entire application (the typical case) then nothing has changed.
This release also includes a refactoring of the way OPTIONS support is implemented. The new implementation should be more efficient because it creates far fewer routes. It also fixes an issue where the silex-cors-provider has to be registered after an other providers that might create routes such as the silex-annotation-provider. Now the providers can be added in any order.
v0.3.0
In this release I added the cors-enabled service. It is now the preferred way to enable CORS support, but the old way still works like it used to. The main benefit is that it works properly for controller collections and controllers. If you enable CORS support for the entire application (the typical case) then nothing has changed.
This release also includes a refactoring of the way OPTIONS support is implemented. The new implementation should be more efficient because it creates far fewer routes. It also fixes an issue where the silex-cors-provider has to be registered after an other providers that might create routes such as the silex-annotation-provider. Now the providers can be added in any order.