I messed around with hand-endcoding oauth urls as well and finally gave up.
There are a plethora of APIs out there that take care of all this for you. Personally I am using @anywhere on the client and twitter4j on the server. Really seamless, and now I can focus my app (www.standard3d.com). On Aug 12, 8:09 am, Lumpizaver <demsarj...@gmail.com> wrote: > I cannot get the oAuth to work properly. > > I am trying to get a web response of a string that looks like > this:https://twitter.com/oauth/request_token? > oauth_callback=http://win.plane.si/TwittRank/tweets.aspx > &oauth_consumer_key=[MY CONSUMER KEY] > &oauth_nonce=8536829 > &oauth_signature_method=HMAC-SHA1 > &oauth_timestamp=1281614745 > &oauth_token=[MY ACCESS TOKEN] > &oauth_version=1.0 > &oauth_signature=OTNQE/CGAcVemax9egTA5LFw04w=} > > I get the exception: The remote server returned an error: (401) > Unauthorized. > > If I visit the URL above in browser i get: > > Failed to validate oauth signature and token > > Thanks for your help. > > Jure