Looking into the TokenAuthentication class I see that the header being checked is 'HTTP_AUTHORIZATION' and not 'Authorization'
Not quite true, when doing lookups in the request META
dict, the headers that it's actually looking for are with out the preceeding HTTP_
, so request.META.get('HTTP_AUTHORIZATION', '')
is actually looking up the Authorization
header in the request.
The problem is that in my unittests the authentication fails
Changing the header to 'HTTP_AUTHORIZATION' seems to work
I havn't double checked how the test client looks but I believe that setting HTTP_AUTHORIZATION
is what you need to do get the equivalent of actually setting the Authorization
header. If you actually made an http request you should find that setting the auth header works exactly as you'd expect.
See request.META
documentation here: https://docs.djangoproject.com/en/dev/ref/request-response/#django.http.HttpRequest.META
Edit:
Django docs on looking up headers in request.META
:
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.
Django docs on setting headers with the test client:
However, you can use keywords arguments to specify some default headers. For example, this will send a User-Agent
HTTP header in each request:
c = Client(HTTP_USER_AGENT='Mozilla/5.0')