Strange error response to #account.rate_limit_status?

9 views
Skip to first unread message

Clive Crous

unread,
Aug 26, 2010, 2:08:04 PM8/26/10
to grac...@googlegroups.com
Hello,

I noticed that my rate limit kept getting in the way of my testing
today so I started printing out the rate_limit_status at the begining
of my test so that I could see how much (in that hour) I have to work
with.

My code to print it out is as follows:

p @client.account.rate_limit_status?

The rate limit check only works on every third or fourth attempt. When
it does succeed I get the following print:

#<Grackle::TwitterStruct remaining_hits=30, reset_time="Thu Aug 26
19:03:22 +0000 2010", hourly_limit=30,
reset_time_in_seconds=1282849402>

( I can't believe I'm only allowed 30 per hour :( is that really normal? )

But mostly I get the following:


....../grackle/client.rb:255:in `rescue in process_response': Unable
to decode response: 705: unexpected token at '<HTML>
(Grackle::TwitterError)
<HEAD><TITLE>302 Moved Temporarily</TITLE></HEAD>
<BODY>
<H1>Moved Temporarily<H1>
<H4>
You are being redirected to a new location because:<P>
[code=BYPASSED_URL] The client request was forwarded directly to the
origin server. No action is required.
</H4>
<HR>
</BODY>
</HTML>
'
from ....../grackle/client.rb:246:in `process_response'
from ....../grackle/client.rb:223:in `call_with_format'
from ....../grackle/client.rb:205:in `append'
from ....../grackle/client.rb:143:in `method_missing'
from test.rb:11:in `<main>'

(where test.rb:11 is the print I pasted near the top)

Thanks,
Clive

Hayes Davis

unread,
Aug 26, 2010, 2:15:03 PM8/26/10
to grac...@googlegroups.com
The rate limit at 30 is due to Twitter phasing out basic auth. More info here: http://countdowntooauth.com/

The 302 issue sounds like an issue with Twitter - probably a temporary one. Grackle will redirect if it gets a legit 3XX response from Twitter. This may be due to the basic auth phase out. If it continues, let me know and I'll investigate further.

Hayes

Clive Crous

unread,
Aug 27, 2010, 5:16:38 AM8/27/10
to grac...@googlegroups.com
On 26 August 2010 20:15, Hayes Davis <ha...@appozite.com> wrote:
> The rate limit at 30 is due to Twitter phasing out basic auth. More info
> here: http://countdowntooauth.com/
> The 302 issue sounds like an issue with Twitter - probably a temporary one.
> Grackle will redirect if it gets a legit 3XX response from Twitter. This may
> be due to the basic auth phase out. If it continues, let me know and I'll
> investigate further.

I'm receiving this same error again. This time using oauth (thanks to
your emails in my other post) and using the following method this
time, not rate check:

client.users.show?( :screen_name => twitter_screen_name )

Clive

Reply all
Reply to author
Forward
0 new messages