Authorization Header Not Recognized by Nginx Server

[Dean Christian Armada]

I was wondering why my Authorization Header is not recognized. When I pass it to my server web app endpoint.

http://i.stack.imgur.com/sqVF3.png

However, when I do it on my localhost it works well

http://i.stack.imgur.com/Tfx9Y.png

These are my request headers:

http://i.stack.imgur.com/1JFSD.png

**PS.**

I am using Django Rest Framewok on my backend and what you see is Google Chrome's Advanced REST Client for testing my APIs. Also please take note that the **CORS HEADERS are allowed** and **Token Authentication** is the method I'm Using as credentials for my endpoints.

You may also check my similar question in StackOverflow: http://stackoverflow.com/questions/37880018/authorization-header-not-recognized-by-nginx-server

[Jeff Tchang]

Why is nginx respond in one and WSGI is responding in another? Is nginx eating up the authorization header or not properly passing it?

--
You received this message because you are subscribed to the Google Groups "Django REST framework" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-rest-fram...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Dean Christian Armada]

I don't really know. The nginx one is my actual production endpoint. The WSGI is my development endpoint. The way I see it, Nginx does not recognizing the authorization header

To unsubscribe from this group and stop receiving emails from it, send an email to django-rest-framework+unsub...@googlegroups.com.