ryanmmmmm commented 9 years ago

Here is some information on the issue. Any way to reproduce in this driver so we can actively address on the REST API backend via error handling or handling of these multiline files properly if needed?

Our Curl example does use the following Multiline json:

https://gist.github.com/ryanmedlin/de374797dbb9c7a89e97

Example Curl Tests using our Test API keys:

https://gist.github.com/ryanmedlin/4fef493114cce8f55e5c

See Notes form Kate on the issue

BIG PROB: Sending JSON not in a single line and causes problems but don’t get an error if there is a new line – you just get partial JSON

Getting a lot of errrors which is good For testing, Aaron was using a "prettified" version of json, over multiple lines so that the json string contains newlines and tab characters. json.stringify() was retaining the newline characters, and he thinks we were only looking at the first line. This was throwing weird errors at him that weren't overly obvious.

ajones commented 9 years ago

@ryan I definitely believe this was a programmer error on the requestOR side not the receiving side. I will create a branch with the new line removal taken out.

ajones commented 9 years ago

Confirmed this was a red herring. You can find multi-line pretty printed JSON being accepted just fine in the multi-line-json branch.

@ryan looking to you to confirm and close

ryanmmmmm commented 9 years ago

Cool closing issue. Thanks!!

ajones / datasnap-node

Datasnap REST Endpoint not handling multiline JSON #1

See Notes form Kate on the issue