Hi Guys
I've seen this too. However. If you re-visit the page a couple of
minutes later it'll load just fine. We had this for @socialiteapp and
whilst the initial load wouldn't work, visiting the page a few minutes
later would work just fine.
Cheers!
-N
On Mar 11, 8:59 am, Tim Haines
While grabbing the latest tweets from the friend timeline I will
occasionally receive the full page HTML to the Twitter - Over capacity
page ('Twitter is over capacity. Too many tweets', etc). This breaks
my JSON parser and causes a nasty error. I pretty sure I'm accurately
checking for HTTP
Cameron's solution looks like a good one at this time. This issue [1] tracks
the problem.
1. http://code.google.com/p/twitter-api/issues/detail?id=220
Doug Williams
Twitter API Support
http://twitter.com/dougw
On Thu, Mar 19, 2009 at 4:10 PM, Cameron Kaiser spec...@floodgap.comwrote:
While
Ah, thanks for the feedback. May I ask how you check for HTML-like
responseText accurately? I think some nice regex would do the trick
but don't want to reinvent any wheels!
On Mar 19, 8:44 pm, Doug Williams d...@twitter.com wrote:
Cameron's solution looks like a good one at this time. This
Nial,
What type of parser are you using? Most parsers will throw an exception if
the content isn't of the expected format.
Doug Williams
Twitter API Support
http://twitter.com/dougw
On Thu, Mar 19, 2009 at 4:50 PM, Nial nia...@gmail.com wrote:
Ah, thanks for the feedback. May I ask how you
On Thu, Mar 19, 2009 at 1:08 PM, Nial nia...@gmail.com wrote:
While grabbing the latest tweets from the friend timeline I will
occasionally receive the full page HTML to the Twitter - Over capacity
page ('Twitter is over capacity. Too many tweets', etc). This breaks
my JSON parser and causes
Nick,
I'm indeed checking HTTP response codes and had expected that errors
would be returned in JSON. Due to the nature of the error (an over
capacity message that's sent out by Apache), I understand why it's in
HTML. I'm using entirely my own code and have written what I would
consider to be a
Ah, thanks for the feedback. May I ask how you check for HTML-like
responseText accurately? I think some nice regex would do the trick
but don't want to reinvent any wheels!
Well, assuming it's anything reasonably syntactic, parsing it for anything
starting with DOCTYPE or HTML (or whitespace
