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
Basically the default supported content_type should also support the charset=utf-8 option (it currently doesn't, so if a client sends a Content-type: application/json; charset=utf-8 header, the API responds with a 415 Unsupported Media Type). This is important IMHO, since some clients (like Android's OkHttp add the charset=utf-8 by default).
Basically the default supported content_type should also support the
charset=utf-8
option (it currently doesn't, so if a client sends aContent-type: application/json; charset=utf-8
header, the API responds with a415 Unsupported Media Type
). This is important IMHO, since some clients (like Android's OkHttp add thecharset=utf-8
by default).So currently the workaround is this:
The text was updated successfully, but these errors were encountered: