Hello, I may have found a bug, but I'm not sure if this is the intended behaviour.
In qx.io.request.Xhr, the JSON parser isn't automatically used when the charset is specified as part of the content-type reply header. The replies from the server have a content type of: application/json; charset=utf8 In qx/io/request/Xhr.js line 373, the string used for detection is: application/json I know the charset is a bit redundant as JSON is always in UTF-8, but it might be good to handle this case. I have worked around this in my code by specifying the parser manually: req.setParser(qx.io.request.Xhr.PARSER["json"]); Regards, Silas ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
