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 you do a post() with unicode data in it, it won't be encoded properly unless you specify a content_type with charset=utf8.
However, the mime type application/x-www-form-urlencoded doesn't officially support a charset property. If the server accepts multiple charsets it has to get that information elsewhere.
I think it might be reasonable to encode any unicode keys or values in a form to UTF-8 by default if there is no content_type or no charset on the content_type.
The text was updated successfully, but these errors were encountered:
When you do a post() with unicode data in it, it won't be encoded properly unless you specify a content_type with charset=utf8.
However, the mime type application/x-www-form-urlencoded doesn't officially support a charset property. If the server accepts multiple charsets it has to get that information elsewhere.
I think it might be reasonable to encode any unicode keys or values in a form to UTF-8 by default if there is no content_type or no charset on the content_type.
The text was updated successfully, but these errors were encountered: