When using OAuth, I get a "401 Incorrect signature" error when doing a statuses/friends_timeline.json?count=1
it works fine without the count parameter. however /statuses/user_timeline.json?count=1 works perfectly. Can somebody confirm? regards, Prashanth On Sat, Sep 12, 2009 at 11:38 PM, Chad Etzel <c...@twitter.com> wrote: > > Hmm, this should not be the case. Is anyone else seeing this issue? > If you continue to see this, please create an issue here: > http://code.google.com/p/twitter-api/issues/list > > Thanks, > -Chad > > On Fri, Sep 11, 2009 at 3:34 PM, Heath<maxim...@gmail.com> wrote: > > > > Our application has been getting 401 errors when attempting to cache > > tweets from the new "Verified Accounts". This includes accounts like > > Mashable (http://twitter.com/mashable). > > > > We are using the user_timeline.xml method, and get the 401 when using > > a white-listed account to avoid default rate limits. > > > > Is this no longer possible when using a whitelist account, or is there > > another method without this restriction? > > >
