You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When making a POST requst – for example when authenticating via /token – API should should accept the request even if charset=UTF-8 is present in the Content-Type header.
For example "Content-Type: application/json;charset=UTF-8"
Actual behavior
API throws an Invalid Credentials error if Content-Type include charset=UTF-8. Common frontend libraries like Axios append charset to Content-Type in POST requests by default.
The text was updated successfully, but these errors were encountered:
jean-luc
changed the title
Allow "Content-Type: application/json;charset=UTF-8" in POST requests
Allow Content-Type to contain 'charset=UTF-8' in POST requests
Oct 11, 2019
Expected behavior
When making a POST requst – for example when authenticating via
/token
– API should should accept the request even ifcharset=UTF-8
is present in theContent-Type
header.For example
"Content-Type: application/json;charset=UTF-8"
Actual behavior
API throws an
Invalid Credentials
error ifContent-Type
includecharset=UTF-8
. Common frontend libraries like Axios append charset to Content-Type in POST requests by default.The text was updated successfully, but these errors were encountered: