Re: [twitter-dev] "Unauthorized: Incorrect signature" for protected users

2010-12-14 Thread Matt Harris
Ni Niklas,

In most of these cases the issue is to do with character encoding,
specifically commas not being encoded as %2C properly. Could you share your
basestring so we can check this.

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


On Tue, Dec 14, 2010 at 3:48 PM, Niklas Hellenbart <
niklas.hellenb...@gmail.com> wrote:

> Hi folks,
>
> every time requesting the follower or friends id-list (api call
> followers/ids & friends/ids) or calling account/verify_credentials
> with valid oauth credentials I get an 401 error "Unauthorized:
> Incorrect signature". Methods like statuses/update using the same
> creden are fine. I tried Zend_Oauth in several versions from a
> whitelisted client but only requests with users that are not protected
> are successful.
> Has anybody similar problems?
>
> ps: the system time is correct
>
> Cheers,
> Niklas
>
> --
> Twitter developer documentation and resources: http://dev.twitter.com/doc
> API updates via Twitter: http://twitter.com/twitterapi
> Issues/Enhancements Tracker:
> http://code.google.com/p/twitter-api/issues/list
> Change your membership to this group:
> http://groups.google.com/group/twitter-development-talk
>

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk


[twitter-dev] "Unauthorized: Incorrect signature" for protected users

2010-12-14 Thread Niklas Hellenbart
Hi folks,

every time requesting the follower or friends id-list (api call
followers/ids & friends/ids) or calling account/verify_credentials
with valid oauth credentials I get an 401 error "Unauthorized:
Incorrect signature". Methods like statuses/update using the same
creden are fine. I tried Zend_Oauth in several versions from a
whitelisted client but only requests with users that are not protected
are successful.
Has anybody similar problems?

ps: the system time is correct

Cheers,
Niklas

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk