Json posts failing with encoding problems in 3.2.11

[timuckun]

When I execute the following

curl -H "Content-Type: application/json" -d '{"data": {"firstname": "Ninh","lastname": "Vo","email": "ninh.vo@texodesign.com","password": "khongtuu","phone": "+84904493642" },  "device_id": "222222" }'  -X POST http://localhost:3000/api/v1/salesperson/register -i

I get the following error

MultiJson::DecodeError (lexical error: invalid char in json text.
          ","phone": "+84904493642" },  "device_id": "222222" }
                     (right here) ------^

The right there is pointing to the quote which is apparently in a non UTF8 encoding.

Removing that quote leads to other errors on other characters so clearly the JSON parser is not coping with the encoding properly.

The full stack trace is here https://gist.github.com/4632520

[steveklabnik]

I cannot reproduce this. When I copy/paste your curl and run it against an app of mine, everything parses correctly. This is against master, anyway.

Are you sure you're not sending strange quote characters?

[steveklabnik]

Also tried on 3.2.11, works just fine.

[timuckun]

It doesn't surprise me that you can't duplicate the problem. Chances are the act of pasting it into this text box converts it somehow.

I don't know what encoding the client is using but he is in Vietnam and is using windows.

[steveklabnik]

😢

GitHub should support UTF8, but given that he's pasting it to you, I assume, the issue might happen between then and now.

Is there any way I can get some way to reproduce this? Otherwise, I can't do anything about it. 😦

[drbrain]

This may be relevant, ruby doesn't support Windows-1258 encoding at this time: https://bugs.ruby-lang.org/issues/7742

[timuckun]

AAAUUUGGGGGHHHH.

On the off chance that I am NOT tripping over this but is there any way to configure rails so that all JSON posts are automatically (and forcefully) converted to UTF8? I can give the client back a sane error message if the conversion is not perfect but currently it causes an exception.

[mikepmunroe]

@timuckun, any update on this? Is it possible that you received more information after your most recent comment that could be of help in trying to reproduce the problem?

[arunagw]

@timuckun closing this issue for now.

Please reopen again if this problem still persist.

thanks