Fix broken links in JSON responses

[jackbravo]

Links inside the a JSON response are not displayed properly because JSON encodes strings.

This fix displays the original url but the underlying link is using the parsed string as the link href property.

This is an example JSON response that has this problem:

{
  "authenticateURL": "https://example.com/auth?reg_code=XLMKJDK\u0026mso_id=ATT",
  "expires": 1592867389703
}

The parsed link should be https://example.com/auth?reg_code=XLMKJDK&mso_id=ATT.

[Huachao]

@jackbravo Merged thanks

[Huachao]

@jackbravo you can try the latest version 0.24.2

[tangdw]

sorry 我没编辑好，我想写的是一个 img

{
"test": "<img src=\"https://shenzhen.aliyuncs.com/aaa/201903/2019032614/file_aaa.jpg\" title=\"\" alt=\"\"/>"
}

@Huachao @jackbravo

[Huachao]

@tangdw the response body you've provided is not JSON actually

{
test: src="[https://aliyuncs.com/asas/201903/2019032614/file_as.jpg"\](https://aliyuncs.com/asas/201903/2019032614/file_as.jpg%22%5C%60)
}

[jackbravo]

Indeed, that is not json, it needs " surrounding both the key and the value.

On the other hand, the new release is working great for me with links on json. Thanks @Huachao !

[Huachao]

@jackbravo @tangdw I got the root cause since @jackbravo will try to JSON parse the links of JSON mime type, here so I think we can simply revert the change and the issue in #676 will be solved. @jackbravo as for your case, I forgot that we already have a setting to handle the escape issue, so you just need to set rest-client.decodeEscapedUnicodeCharacters": true in the previous and future versions when I publish a new version

[jackbravo]

😮 ! Didn't know about that option. But should work as well.