I have been reading about jwt and a few times there has been mention of using the http header Authentication to pass the jwt token to the server. This is especially true when reading about angular and jwt. Yet, I've been using a custom header: x-access-token.
I'm wondering if there is a reason to switch to this header. The documentation about the Authentication header http://tools.ietf.org/html/rfc1945#section-10.2 suggests it's to be used for specific reasons, but I can't tell if it does anything special like encrypt it first.
I have been reading about jwt and a few times there has been mention of using the http header
Authenticationto pass the jwt token to the server. This is especially true when reading about angular and jwt. Yet, I've been using a custom header:x-access-token.I'm wondering if there is a reason to switch to this header. The documentation about the Authentication header http://tools.ietf.org/html/rfc1945#section-10.2 suggests it's to be used for specific reasons, but I can't tell if it does anything special like encrypt it first.