Bug when converting response to JSON: it seems like the JSON errors are not processed and an error in the conversion result in a 200 response with invalid JSON. Also incoming json errors are not processed, resulting in a crash
Final Release Note
Description
By supplying an invalid response (like a $char(0) terminated string it should trigger a JSON conversion error. Instead, it return 200 and response is an invalid JSON
In this situation, passing a string called "secondary" which is a $char(0) terminated character, we get the following JSON back:
ber":61,"Secondary Instance Name":"santiago"}]}},"secondary2":}"
As you can see, secondary2 does NOT have a string
"secondary2":}
making it a bad json....
This error will occur also when invalid chars are used in strings (like UTF-8)
This error should be trapped by the error handler and be returned in the JSONERR array... It seems that the error array doesn't get processed...
NEED TO BE TESTED ALSO WITH A BAD JSON IN THE REQUEST BODY, as it crashes instead of returning a 400 Bad Request