server (or client) corrupt UTF8 asset descriptions

[unsystemizer]

• If a UTF8 string is passed, it's completely dropped (empty) somewhere along the way
• If an ASCII-fied (e.g. \uXXXX or other) encoding is used, it's taken literally (it should be converted to UTF8 before it's passed to server/lib.)

I debugged this:

• the client sends "description": "\uXXXX\uXXXX..." to the server.
• when I request asset info which has UTF-8 in description, the server returns "description": "\uXXXX", so it should probably also accept such encoding as well
• Werkzeug seems to default to UTF-8, so for now I can't see what else to try. I tried passing utf-8 in Content-Headers, didn't help.

For now I'll just save these notes for later.

[unsystemizer]

Updated to requests 2.15.2, now in Ubuntu 16 UTF-8 Bash the first double byte char into description properly, the rest are simply discarded. Slightly better than before.

[chiguireitor]

Is this an issue on the rpc end?