Well at least it's not just me, I was very worried esp with the
"Clients may not make more than 0
requests per hour." That I'd some how managed to blacklist myself

On Jan 28, 11:23 pm, Zaudio <si...@z-audio.co.uk> wrote:
> Hi,
>
> I'm getting this back and just do not understand why:
>
> TWITTER LOG GENERATED ON 28/01/2010 3:57:57 PM
> ----------------------------------------------------------------------------
> ExecuteGetCommand:
> Twitter reported Error (OAuth): The remote server returned an error:
> (400) Bad Request.
> Request 
> url:http://api.twitter.com/1/friends/ids.xml?user_id=35034625&cursor=-1
> <?xml version="1.0" encoding="UTF-8"?>
> <hash>
>   <request>/1/friends/ids.xml?
> cursor=-1&amp;oauth_consumer_key=XXXXXXXXXXXXXXXXX&amp;oauth_nonce=35034625____546_490163&amp;oauth_signature_method=HMAC-
> SHA1&amp;oauth_timestamp=1264719478&amp;oauth_token=35034625-
> XXXXXXXXXXXXXXXXXXXX&amp;oauth_version=1.0&amp;user_id=35034625&amp;oauth_signature=XXXXXXXXXXXXXXXX</
> request>
>   <error>Rate limit exceeded. Clients may not make more than 0
> requests per hour.</error>
> </hash>
>
> Response Headers: X-RateLimit-Limit: 0
> Status: 400 Bad Request
> X-RateLimit-Remaining: 0
> X-Runtime: 0.02385
> X-RateLimit-Class: api_identified
> X-RateLimit-Reset: 1264723053
> Vary: Accept-Encoding
> Connection: close
> Content-Length: 507
> Cache-Control: no-cache, max-age=1800
> Content-Type: application/xml; charset=utf-8
> Date: Thu, 28 Jan 2010 22:58:35 GMT
> Expires: Thu, 28 Jan 2010 23:28:34 GMT
> Set-Cookie:
> _twitter_sess=BAh7BzoHaWQiJTdhNzJkYmNkYWQzZTM3OGMzOGZiODc3ODllMmUzMTFhIgpm
> %250AbGFzaElDOidBY3Rpb25Db250cm9sbGVyOjpGbGFzaDo6Rmxhc2hIYXNoewAG
> %250AOgpAdXNlZHsA--5b92ace9ec11f25bd06a6b1812e05e9550852992;
> domain=.twitter.com; path=/
> Server: hi
>
> -----------------
> I've tested rate limits for my local testing IP (216.45.124.14 )
> where I'm getting this, and my testing account Zaudio... and the test
> user Zaudio2  - all looks good
>
> Please urgently address this. I thought it a blacklisting issue... but
> maybe it's a bug?
>
> Thanks
>
> Simon (Zaudio)
> Developerwww.bullsonwallstreet.com

Reply via email to