Can you give an example of the HTTP headers or OAuth query parameters you're sending along with both variations of the request? While it's not required, I recommend explicitly specifying a user_id or screen_name for these methods, instead of relying on the magic implicit user that auth brings you. I also recommend sticking to HTTP header-based auth, as it dramatically separates concerns.
Your resource-specific query parameters should be added to the URL before you compute your signature -- in your signature base string, the query parameters should be sorted. Thanks, Taylor @episod <http://twitter.com/episod> - Taylor Singletary On Tue, Apr 12, 2011 at 5:13 AM, Randomness <randomness.bl...@gmail.com>wrote: > I wrote some code that retrieves tweets sent by an authenticated user > which works fine. As the resource I use: > > http://api.twitter.com/1/statuses/user_timeline.xml > > which is used for te base string. For the CURLOPT_URL I added paramers > to the URL like: > > ?count=200&page=1&include_rts=true > > From the documentation I figured that retrieving mentions works > exactly the same, only the resource needs to be changed to: > > http://api.twitter.com/1/statuses/mentions.xml > > This is the only change I made to the code, all else remains exactly > the same. Instead of retrieving my mentions I get the message > "Incorrect signature". > > I have been staring at my code for a while now, and don't see what is > wrong. > > Anyone any suggestions or an explanation? > > > -- > 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
