API should accept RFC7235 authorization header

hexpm / specifications

Specifications for using and implementing Hex protocols

48 stars 26 forks source link

API should accept RFC7235 authorization header #34

Closed viceice closed 3 years ago

viceice commented 3 years ago

Currently HEX API requires authorization: <token> as api header, it should support normal Bearer token as other API's will do.

curl --include \
     --header "Accept: application/json" \
     --header "Authorization: Bearer <token>" \
  'https://private-anon-d3fb121a9d-hexpm.apiary-mock.com/packages?sort=&search='

renovatebot/renovate#11028
renovatebot/renovate#11168
https://datatracker.ietf.org/doc/html/rfc7235#appendix-C

ericmj commented 3 years ago

Agreed. We need to implement it in a backwards compatible way on https://github.com/hexpm/hexpm first then the specifications can be updated.

ericmj commented 3 years ago

Closing this since it requires functionality change before the specs can be updated.