Log in from the front page. I'm getting the same thing from
twitter.com/login, but the front page is doing the trick.
On Aug 7, 9:30 pm, d d cawah...@gmail.com wrote:
I figured that maybe it was just a glitch with a few accounts but it
would appear that it has singled me out because I do not
Is there a way to force Twitter's API to respond with a particular
HTTP response code? I'd like to make sure that if there happens to be
a 500 error, my app isn't going to crash/infinite loop/collapse into a
black hole and consume the Earth. I can probably fake it in my app,
but I wanted to test
But your users all have to reauthenticate against what is technically
a new app in the system. And if you do anything offline from the user,
you won't have access under the new OAuth key to their account.
On Dec 23, 7:01 pm, shiplu shiplu@gmail.com wrote:
On Thu, Dec 24, 2009 at 3:45 AM,
probably simulate certain error conditions (when we throw 404s and
the like), and you can probably force it to get to a rate limit error - but
a particular 500 error, no.
On Wed, Dec 23, 2009 at 4:43 PM, Tim Dorr timd...@gmail.com wrote:
Is there a way to force Twitter's API to respond
a full test, then you would
have to pass a different parameter you would never pass in production, etc.,
etc.
On Wed, Dec 23, 2009 at 9:04 PM, Tim Dorr timd...@gmail.com wrote:
Well, as a recommendation, a parameter similar to
suppress_response_codes would be very helpful for complete
