For clarity: There is nothing stopping you from using localhost as your oauth_callback during testing for OAuth 1.0a. While the form for your application on dev.twitter.com will not allow you to store a localhost domain as your pre-registered callback URL, our OAuth sub-system has no trouble using localhost for redirects when explicitly declared on the request token step. If you want to use localhost as your domain, just set the callback URL within your application record to something else.
As a reminder, it's proper OAuth to always send an oauth_callback on the request token step of OAuth negotiation -- even if you've preregistered a callback or are using the PIN code/out-of-band flow (in which case you would send oauth_callback=oob). Taylor On Mon, Aug 9, 2010 at 5:53 AM, Lumpizaver <demsarj...@gmail.com> wrote: > I also have a problem with this. > > I cannot use the twitter API login with OAuth when I am debugging on > localhost. > I tought that it is not possible to use Twitter authentication on > localhost because of the callback url. > So I tought that I have to upload my site somewhere before. > > Sincerely, Jure > > On 8 avg., 07:30, punit khaire <punit.kha...@gmail.com> wrote: > > Thanks Tom, > > > > I am using localhost to tweet messages but it is giving error message as > > Failed to authenticate with oauthe signature and token.Is this happening > > because I had given callback URL.I am generating proper signature and > > sending all parameters. > > > > I am not getting where I am going wrong . > > > > Punit. > > > > > > > > On Sun, Aug 8, 2010 at 5:13 AM, Tom <allerleiga...@gmail.com> wrote: > > > Yes, you can. Any application that can sign oAuth requests can send > > > tweets. > > > > > Tom > > > > > On Aug 7, 2:44 pm, "Punit.khaire" <punit.kha...@gmail.com> wrote: > > > > Can we use localhost to tweet messages using oAuth authentication?? >
