-
-
Notifications
You must be signed in to change notification settings - Fork 536
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CorsMiddleware is not working in Django 1.10 #102
Comments
I made some initial progress on Django 1.10 support in this project's more maintained fork: If someone wants to finish it up before I get a chance to double back and do so myself, feel free :-) |
Thanks. I didn't know there's more active forks. Then, I close this issue. |
I'd perhaps leave this open, to make it clearer to those finding this project, that it doesn't support Django 1.10? |
Sure, no problem! |
@adrysn did you mean this project is not maintained anymore? |
@adrysn Thanks alot, your post have saved me after hours of debugging and surfing the internet for solutions on the CorsMiddleware issue with django 1.10 |
Apparently django-cors-headers is no longer maintained, django-cors-middleware is a good alternative: |
@devalfrz, thanks |
Can we please mention this in the README of this project. After spending so much time with this repo, there is no way to know that django-cors-middleware is being maintained and we are stuck with the |
I've emailed @ottoyiu asking to be added as a maintainer but no reply |
Now I've been added as maintainer (see #110) I've merged Django 1.10 support, and deployed to PyPI at version 1.2.0. Enjoy. |
Should we consider closing this issue then? (Haven't checked it myself though). |
This issue is closed 😄 . We are still upgrading to 1.10 at work but |
Ahh, didn't notice that. Sorry! 😝 |
CorsMiddleware is not working with Django 1.10. If it is inserted into the list of middlewares in settings file, an error occurs such as below.
This error is probably due to the changed style of middleware introduced in Django 1.10:
https://docs.djangoproject.com/en/1.10/topics/http/middleware/.
The middleware class should be updated to comply with the new style.
For the moment, one can replace
object
toMiddlewareMixin
to enable the middleware.The text was updated successfully, but these errors were encountered: