Sanic-cors

Latest version: v2.2.0

Safety actively analyzes 621420 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 1 of 9

3.0.2

Fixes Issue 187: regression whereby header (and domain) matching was incorrectly case sensitive. Now it is not, making the behavior identical to 2.X and 1.X.

3.0.1

Fixes Issue 183: regression whereby regular expressions for origins with an "?" are not properly matched.

3.0.0

This release is largely a number of small bug fixes and improvements, along with a default change in behavior, which is technically a breaking change.

**Breaking Change**
We added an always_send option, enabled by default, which makes Sanic-CORS inject headers even if the request did not have an 'Origin' header. Because this makes debugging far easier, and has very little downside, it has also been set as the default, making it technically a breaking change. If this actually broke something for you, please let me know, and I'll help you work around it. (156) c7a1ecdad375a796155da6aca6a1f750337175f3


Other improvements:
* Adds building of universal wheels (175) 4674c3d54260f8897bd18e5502509363dcd0d0da
* Makes Sanic-CORS compatible with OAuthLib's custom header class ... (172) aaaf904845997a3b684bc6677bdfc91656a85a04
* Fixes incorrect substring matches when strings are used as origins or headers (165) 9cd3f295bd6b0ba87cc5f2afaca01b91ff43e72c
* Fixes logging when unknown options are supplied (152) bddb13ca6636c5d559ec67a95309c9607a3fcaba

2.2.0

- Quick dirty fix for new middleware-registry behaviour on sanic v22.9.0, fixes 64
- Vary 'Origin' header will be added to any existing Vary string on response, fixes 62

2.2.0b1

- Quick dirty fix for new middleware-registry behaviour on sanic v22.9.0

2.1.3

Fixes Vary:Origin header sending behavior when regex origins are used.

Page 1 of 9

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.