Error starting today

25 views
Skip to first unread message

cootcraig

unread,
Jan 5, 2011, 1:25:59 PM1/5/11
to Grackle Development
Just a temporary glitch?

get http://api.twitter.com/1/favorites.json?include_entities=1&page=1
=> 401: {"request":"\/1\/favorites.json?
include_entities=1&page=1","error":"Timestamp out of bounds"}

cootcraig

unread,
Jan 5, 2011, 1:29:20 PM1/5/11
to Grackle Development
Also

get
http://api.twitter.com/1/statuses/user_timeline.json?include_rts=true&count=40&include_entities=1&page=1&screen_name=CootCraig&trim_user=true
=> 401: {"request":"\/1\/statuses\/user_timeline.json?
include_rts=true&count=40&include_entities=1&page=1&screen_name=CootCraig&trim_user=true","error":"Timestamp
out of bounds"}

cootcraig

unread,
Jan 5, 2011, 1:31:02 PM1/5/11
to Grackle Development
Also

get http://api.twitter.com/1/statuses/friends.json?cursor=-1 => 401:
{"request":"\/1\/statuses\/friends.json?cursor=-1","error":"Timestamp
out of bounds"}

Hayes Davis

unread,
Jan 5, 2011, 2:48:11 PM1/5/11
to Grackle Development
This looks like a transient Twitter error. I'd check the Twitter Dev
Group[1] to see if anyone else is experiencing this issue.

Hayes

[1] http://groups.google.com/group/twitter-development-talk

On Jan 5, 10:31 am, cootcraig <cr...@coot.net> wrote:
> Also
>
> gethttp://api.twitter.com/1/statuses/friends.json?cursor=-1=> 401:

cootcraig

unread,
Jan 5, 2011, 5:41:08 PM1/5/11
to Grackle Development

> This looks like a transient Twitter error. I'd check the Twitter Dev
> Group[1] to see if anyone else is experiencing this issue.
>
Here's the reply I got. I'm not aware I'm sending a timestamp.

=========================
Hey Craig,

There are no known issues with timestamps. What is the timestamp you
are
sending to us?

If your timestamp isn't close to the time of our servers (GMT) we will
throw
this error.

Best,
@themattharris
Developer Advocate, Twitter
http://twitter.com/themattharris

Hayes Davis

unread,
Jan 5, 2011, 5:56:00 PM1/5/11
to grac...@googlegroups.com
Ah, I spoke too soon. This is most likely related to OAuth since 401 means you're unauthorized. As part of each authenticated request, grackle (via the required OAuth gem) generates a timestamp and uses that as part of the signature that is sent to Twitter in an HTTP header. If your computer's time is far off from Twitter's then you'll see this error. You should check your computer's time. 

Also, what version of the OAuth gem do you have installed?

Hayes

cootcraig

unread,
Jan 5, 2011, 8:40:46 PM1/5/11
to Grackle Development

On Jan 5, 3:56 pm, Hayes Davis <ha...@appozite.com> wrote:
> Ah, I spoke too soon. This is most likely related to OAuth since 401 means
> you're unauthorized. As part of each authenticated request, grackle (via the
> required OAuth gem) generates a timestamp and uses that as part of the
> signature that is sent to Twitter in an HTTP header. If your computer's time
> is far off from Twitter's then you'll see this error. You should check your
> computer's time.
>

Yes, syncing my time fixed it. This was pointed out by someone on the
twitter dev. group.
My development box is Ubuntu running in a VMware image, I'm guessing
the time is off when
after I suspend and then resume.

> Also, what version of the OAuth gem do you have installed?

oauth (0.4.4)
Reply all
Reply to author
Forward
0 new messages