HTTP_ORIGIN is empty so origin is False all the time about django-cors-headers HOT 11 CLOSED

Origin is sent by your browser on cross-origin requests only: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Origin .

from django-cors-headers.

I have this problem when I am running locally using runserver (the django dev server).

Same fix worked.

What's the prognosis for an "official" fix? I'd rather stick with what seems to be the main source. Pip install and all.

from django-cors-headers.

P.S. this issue only affects the local django dev server. Works fine on Apache without the fix. So I'm not inclined to fork it.

from django-cors-headers.

@bhaugen What version of apache you use? I have apache 2.2.31 and there are no "Origin" header there. From where it come from?

from django-cors-headers.

@angry-elf - we deploy on Webfaction. Apache 2.something. I have no server fu, which is why we deploy on Webfaction. So I can't explain very much here. Sorry to disappoint. Maybe somebody else can come along and enlighten both of us.

from django-cors-headers.

@bhaugen
just realized, i need cors headers at other side of requests, so i don't need it in my application at all :)

from django-cors-headers.

I think that's right. I just needed
CORS_ORIGIN_ALLOW_ALL = True
CORS_ALLOW_CREDENTIALS = True
for selected URLs.

Which is what django-cors-headers supplies.

from django-cors-headers.

Sounds like this issue was fixed.

from django-cors-headers.

Hi,
in the current release,
on process_response function in corsheaders/middleware.py
origin = request.META.get('HTTP_ORIGIN') is always empty, so
response["Access-Control-Allow-Origin"] is impossibile to set.

Just to be sure, it's correct because I'm in development mode?

Thanks
Pietro

from django-cors-headers.

Thank you ...
Clearly, I need to sleep ...

from django-cors-headers.

Hi!
I have this problem on Django 2.2.3 while running both the back end and the front end in localhost, si there any workaround to make it work ?

from django-cors-headers.