Fails to show non-JSON parse-able response

[mortias]

Hello,

Refr @webron @ponelat

We identified a possible regression bug related to the "no content" bug

Basically if the json returned is invalid, in previous versions you got the response back
anyway but it told me that it was not able to parse it, now i yust get "no content"

For security reasons we prefix our json responses with
)]}',
{"header":{"code":200,"text":"OK","version":"1.0"},"data":"some data"}

[mortias]

ok, we figured out that the thirdparty libs are not relaiable so the only option would be to force the ui to use jquery, meaning set the option useJQuery : true in the SwaggerUI constructor on the index.html

[ponelat]

Here is the issue for superagent...
ladjs/superagent#675

[webron]

This should no longer be an issue in 3.X.