Hi Volkert,
Thanks for the test case, it helped me figure out what the problem was.
Basically, what Norbert said was 100% correct: the server code (Teapot) should
have specified the charset or encoding of the mime-type it was using (so
application/json;charset=utf-8 instead of just
Understand. Anyway, in Teapot it should possible to set the UTF-8
charset for JSON documents.
Thanks,
Volkert
Am 02.05.2015 um 20:34 schrieb Sven Van Caekenberghe:
Hi Volkert,
Thanks for the test case, it helped me figure out what the problem was.
Basically, what Norbert said was 100%
Dear all,
i am trying to get a JSON Document with ZnEasy. The Document is UTF-8
encoded.
(ZnEasy get: 'http://removed/api/atm/801813') entity string.
Any hints?
Volkert
I tried ZnClient new get: 'http://removed/api/atm/801813'; yourself
and got.
This is the Doc i see in Firefox.
The JSON is served with ZnServer / Teapot. ;-)
Volkert
Am 01.05.2015 um 12:21 schrieb Sven Van Caekenberghe:
Hi Volkert,
Tip 1: use ZnClient and inspect the response in
You need to look at the headers of the request. I would assume the sender sets
an Content-Type: application/json without charset. In that moment it is
uncertain what has to be done because the server needs to assume what charset
it might be and this tasks seldomly works out good.
In order to
