adamchainz / django-cors-headers

Django app for handling the server headers required for Cross-Origin Resource Sharing (CORS)

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Is CORS_ALLOW_ALL_ORIGINS differ from CORS_ORIGIN_ALLOW_ALL ?

Khumayun opened this issue · comments

Wasted 2 weeks spent for fixing an issue with cors finally ended with changing CORS_ALLOW_ALL_ORIGINS to CORS_ORIGIN_ALLOW_ALL. I have dedicated front-end and back-end production servers on different machines and my development pc.
When I ran project on dev. pc with 0.0.0.0 front-end worked perfect, however when I route front-end to production server CORS error occured. I don't understand why this happen, but there is no any article on the web discussing this problem.
Documentations says Previously this setting was called CORS_ORIGIN_ALLOW_ALL, which still works as an alias, with the new name taking precedence. but it worked vice versa(on dev. pc worked both ways)

Hi, this was simply a rename. It was spelled out well in the changelog. If you've had issues, perhaps they are due to using different versions on different servers.