Your Base String seems fine and the parameters in your URL look fine as well. However, like I said: try executing the request with code, not in your browser.
That, and I'm not entirely sure about how Twitter's OAuth implementation works. You may have to send the oauth_* parameters in the Authorization: header. Tom PS: Why all the German words? On 9/21/10 11:17 AM, andy wrote: > Hello again, > > I gerausgefunden that I need to create a new Response xauth after > signing with my access_token. And I have a new basestring, looks like > this: > > GET&http%3A%2F%2Fapi.twitter.com%2F1%2Fstatuses > %2Ffriends_timeline.xml&oauth_consumer_key%3D.........%26oauth_nonce > %3D61A491E6-57D4-F561-9B14-33906AD0D04E%26oauth_signature_method > %3DHMAC-SHA1%26oauth_timestamp%3D1285060323%26oauth_token > %3D.............%26oauth_version%3D1.0 > > my signing Key is this: > > myConsumerSecret&myTokenSecret > > After creating a new Signature, I will send a Request to the URL > http://api.twitter.com/1/statuses/friends_timeline.xml with following > GET-Parameter: > > oauth_consumer_key=.....&oauth_nonce=61A491E6-57D4- > F561-9B14-33906AD0D04E&oauth_signature=5C1ZtFJi2AjnoSoyWkCZkeIBLA4=&oauth_signature_method=HMAC- > SHA1&oauth_timestamp=1285060323&oauth_token=.................&oauth_version=1.0 > > It opens another window where I enter my user data and then I get > again an request-error. > -- 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?hl=en
