It doesn't allow you to set http://localhost/ or http://127.0.0.1 as a callback URL. This is rather frustrating because I don't want to have to make a fake host and make all my developers make the same fake host on their respective machines as well, just to get something trivial like this to work.
On Apr 27, 1:08 pm, Paul Kinlan <paul.kin...@gmail.com> wrote: > This is going to sound silly, but I had it with a port on the settings page > > I addedhttp://www.twedaq.com:8080/oauthin to the oauth conf page, and then > changed my host file and all worked really well. > > Paul > > 2009/4/27 Benjamin Cox <b...@insourcery.com> > > > > > Unfortunately, I'm working on a dev machine that's doubling as a web > > server for another small project. I simply cannot run on port 80 in > > development. > > > Does that mean there is no way I can test oauth integration with > > Twitter? Would you consider adding the ability to put a port number > > in the callback URL on the settings page? > > > Please? > > > Cheers, > > > Ben > > > On Apr 26, 11:41 pm, Paul Kinlan <paul.kin...@gmail.com> wrote: > > > I managed to set a port on the page when I was doing some google app > > > engine stuff. > > > > But saying that my dev server now runs on port 80 on my machine so it > > > isn't a problem much. > > > > Paul > > > > On 27 Apr 2009, at 06:58, Dimebrain <daniel.cre...@gmail.com> wrote: > > > > > How are you able to set this up for a non-standard port? HOSTS file is > > > > just for the domain/authority, and you can't specify a port in the > > > >callbackURL on the settings page? > > > > > On Apr 23, 7:31 pm, Jochen Kaechelin <giss...@gissmog.de> wrote: > > > >> Am 24.04.2009 um 00:29 schrieb Paul Kinlan: > > > > >>> Hi, > > > > >>> During development I tend to modify my hosts file to point the > > > >>>callbackURL domain to my box for instance. This is quite good > > > >>> because all it affects is my box. > > > > >> I just had the same idea ... ;-) > > > > >> Works as expected now!!! > > > > >> Thanx > > > > >>> Paul > > > > >>> On 23 Apr 2009, at 23:16, Abraham Williams <4bra...@gmail.com> > > > >>> wrote: > > > > >>>> The oauth_callback parameter was just disabled do to security > > > >>>> issues. Currently only the registeredcallbackworks. If you need a > > > >>>> differentcallbacklocation for development set up a second > > > >>>> application. > > > > >>>> On Thu, Apr 23, 2009 at 17:12, Jochen Kaechelin > > > >>>> <giss...@gissmog.de> wrote: > > > > >>>> Am 22.04.2009 um 15:37 schrieb Abraham Williams: > > > > >>>>> Also when you are building the authorize url to send users to > > > >>>>> twitter.com you can add "&oauth_callback=http://localhost/ > > > >>>>>callback" > > > >>>>> and that will override your applications registeredcallback. > > > > >>>> OAuth::Consumer.new("xxxxxxxxxx", "xxxxxxxxxx", > > > >>>> { :site=>" > >http://twitter.com/oauth/authorize?oauth_callback=http://localhost:30 > > > >>>> ... > > > >>>> " }) > > > > >>>> I can see the site where I have to Deny or Allow access. > > > >>>> When I click "Allow" I will be redirected to the Domain which I > > > >>>> entered in the > > > >>>> OAUTHClients Registration Form (http://www.twitter.com/ > > > >>>> oauth_cleints) > > > > >>>> Seems that the oauth_callback parameter does not work! > > > >>>> Is it in the wrong place? > > > > >>>> Any hints!? > > > > >>>> Thanx > > > > >>>> -- > > > >>>> Abraham Williams |http://the.hackerconundrum.com > > > >>>> Hacker |http://abrah.am|http://twitter.com/abraham > > > >>>> Web608 | Community Evangelist |http://web608.org > > > >>>> This email is: [ ] blogable [x] ask first [ ] private. > > > >>>> Sent from Madison, Wisconsin, United States
