v0.7.1

This release corrects a deprecation warning related to autoloading. It also brings some test and CI configuration up to date. There are no functional changes.

Thanks to @adlacruzes for the fix.

v1.6.1

This release corrects a deprecation warning related to autoloading. It also brings some test and CI configuration up to date. There are no functional changes.

Thanks to @adlacruzes for the fix.

v0.7.0

The primary purpose of this library is to implement CORS. But, it's secondary purpose is to generate OPTIONS routes with Allow headers. This release decouples this secondary functionality so it can be used independently from the CORS functionality. You can now add OPTIONS routes or just an Allow header without including CORS.

v1.6.0

The primary purpose of this library is to implement CORS. But, it's secondary purpose is to generate OPTIONS routes with Allow headers. This release decouples this secondary functionality so it can be used independently from the CORS functionality. You can now add OPTIONS routes or just an Allow header without including CORS.

v1.5.0

This release adds a the ability to specify a protocol when using a wildcard domain. For example, you can now set cors.allowOrigin to http://*.example.com.

Thanks to @brettt89 for bringing this up!

v0.6.0

This release adds a the ability to specify a protocol when using a wildcard domain. For example, you can now set cors.allowOrigin to http://*.example.com.

Thanks to @brettt89 for bringing this up!

v1.4.2

The CORS specification defines "null" as the value for the Access-Control-Allow-Origin header when an origin is rejected. However, it turns out that there are ways for this to be exploited. Thanks to @slipo for bringing this to my attention and providing a patch.

v0.5.2

The CORS specification defines "null" as the value for the Access-Control-Allow-Origin header when an origin is rejected. However, it turns out that there are ways for this to be exploited. Thanks to @slipo for bringing this to my attention and providing a patch.

v1.4.1

Bug fix: Preflight request was not working for /

Everything was working correctly except the response code was 405 instead of 200.

v0.5.1

Bug fix: Preflight request was not working for /

Everything was working correctly except the response code was 405 instead of 200.