Should we be checking for 'Origin' instead of HTTP_ORIGIN? about django-cors-headers HOT 5 CLOSED

+1

from django-cors-headers.

Looking in to that now.. will update with the decision.

from django-cors-headers.

+1

from django-cors-headers.

sorry, I haven't had the time to look at it yet... :( is this a show stopper for a lot of you? If it is, I'll try to make sure I get the time this weekend to figure something out.

from django-cors-headers.

Going to be closing this issue, since it's a non-issue as quoted:

With the exception of CONTENT_LENGTH and CONTENT_TYPE, as given above, any HTTP headers in the request are converted to META keys by converting all characters to uppercase, replacing any hyphens with underscores and adding an HTTP_ prefix to the name. So, for example, a header called X-Bender would be mapped to the META key HTTP_X_BENDER.

https://docs.djangoproject.com/en/dev/ref/request-response/#django.http.HttpRequest.META

Hence the Origin header is actually mapped to the HTTP_ORIGIN key in requests.META.

from django-cors-headers.