This sounds like the same issue many of us have been reporting where
we get back HTML data instead of the expected JSON or XML response...
I expect if you added logging to collect the raw response you would
find it looks like the responses detailed in the tickets below... We
get a similar parsing
I ran some tests from our RightScale instances and sent the guys at
a...@twitter.com some curl traces and tcpdump data that I was able to
capture.
It does appear to happen when some period of time has lagged and
twitter isn't hit. But after a few requests, the problem no longer
manifests
Hi All,
Just want to make sure we're all on the same page here...
By malformed JSON, do you mean stuff that looks like json, but the
parser barfs on it
or
do you mean We're getting back HTML when we're expecting JSON
The data dump that Matt sent us was the latter, but I was wondering if
Craig
Chad: I don't know at this point.
The error occurs on our iPhone app and we don't log anything
(performance memory reasons.) I haven't been able to generate the
error in my test environment (where I can log stuff.)
BUT getting back HTML when we're expecting JSON makes sense to me.
I've feed
