EDIT: Check if the api you’re interacting with is set to Content-Type: application/json, &/or if your client http library is both stringify-ing and parsing the http request body behind the scenes. My client library was generated by swagger, and was the reason I needed to apply these hacks, as the client library was stringifying my pre-stringified body (body: “jsonString”, instead of body: { ...normal payload }). All I had to do was change the api to Content-Type: text/plain, which removed the JSON stringify/parsing on that route, and then none of these hacks were needed. You can also change only the "consumes" or "produces" portion of the api, see here.

原文:如果你的谷歌一直登陆你这里，你的api抛出错误，除非你的JSON双引号转义("{\"foo\": true}")，所有你需要做的是stringify两次，例如JSON.stringify(JSON.stringify(bar)))

看起来这真的是一个古老的帖子:-)但是伙计们，我对此最好的解决办法，是100%的工作，没有复杂的代码，是使用编码/解码到base64的两个函数。它们是atob()和btoa()。到目前为止，最简单和最好的方法，没有必要担心如果你错过了任何字符转义。

乔治

如果您的服务器端脚本是PHP，请使用json_encode()， Json_encode()转义换行符和其他意想不到的标记 (如果不使用PHP，请为您的脚本语言寻找类似的函数)

然后在JavaScript中使用$.parseJSON()，完成!

我在我的一个Ajax调用中得到了相同的情况，其中JSON由于Textarea字段中的换行符抛出了一个错误。这里给出的解决方案对我没用。 所以我使用Javascript的.escape函数，它工作得很好。然后，为了从JSON中检索值，我使用.unescape进行了反转义。

在JSON.stringify上还有第二个参数。所以，更优雅的解决方案是:

function escape (key, val) {
    if (typeof(val)!="string") return val;
    return val
      .replace(/[\"]/g, '\\"')
      .replace(/[\\]/g, '\\\\')
      .replace(/[\/]/g, '\\/')
      .replace(/[\b]/g, '\\b')
      .replace(/[\f]/g, '\\f')
      .replace(/[\n]/g, '\\n')
      .replace(/[\r]/g, '\\r')
      .replace(/[\t]/g, '\\t')
    ; 
}

var myJSONString = JSON.stringify(myJSON,escape);

EDIT: Check if the api you’re interacting with is set to Content-Type: application/json, &/or if your client http library is both stringify-ing and parsing the http request body behind the scenes. My client library was generated by swagger, and was the reason I needed to apply these hacks, as the client library was stringifying my pre-stringified body (body: “jsonString”, instead of body: { ...normal payload }). All I had to do was change the api to Content-Type: text/plain, which removed the JSON stringify/parsing on that route, and then none of these hacks were needed. You can also change only the "consumes" or "produces" portion of the api, see here.

原文:如果你的谷歌一直登陆你这里，你的api抛出错误，除非你的JSON双引号转义("{\"foo\": true}")，所有你需要做的是stringify两次，例如JSON.stringify(JSON.stringify(bar)))