Latest version of the lib in pypi still doesn't support Django 2.0

Hi

I was having a problem with unable to invoke my APIs a while ago. Chrome tells me

my site has been blocked by CORS policy: No ‘Access-Control-Allow-Origin’ header is present on the requested resource

However, another service of mine doesn’t have any problem. I figured out that because the problematic service was using Django 2.0 while another one was using 1.11.x.

So I downgraded it, and everything works fine now. Hence, it’s written in README that the lib was tested with Django 2.0 already so people would think it now supports Django 2.0

[adamchainz]

Hi, the unit tests are 100% passing on Django 2.0 so there must be something more to your error report. If you can dig further and find what the problem is, that would be great - I don’t have much time to maintain this library.

[ghost]

Hum, I will try if I have the time but that will take a long time and I have a workaround for now (I use uwsgi instead of runserver). runserver is the only affected component, other server process work fine. If I have the time, I will “bisect” around the introduction of HTTP 1.1 in runserver, it is the main new functionality of runserver.

Le jeu. 22 févr. 2018 à 14:28, Adam Johnson [e-mail] a écrit :

If you can reproduce it reliably enough, you could try using git bisect to find the exact commit in django where the problem occurs. The Django docs have a guide: https://docs.djangoproject.com/en/dev/internals/contributing/triaging-tickets/#bisecting-a-regression

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/ottoyiu/django-cors-headers/issues/281#issuecomment-367680478, or mute the thread https://github.com/notifications/unsubscribe-auth/Agcu09uLBdAqnpv0GeKlGNksm4kaStMoks5tXWuGgaJpZM4RWpW6 .

–

Christophe Gabard

Lead Developer

06.19.14.48.15

[e-mail]

[image: logo-papernest] http://www.papernest.com/?source=signature_email