OMG, love u dude! Thanks a lot... the library I was using was sending an empty callback, I had to fill it with the right call back.
That's strange, I wonder why I should register the callback on twitter too if I can specify when requesting the token! Thanks a lot Chad! On Aug 14, 5:59 pm, Chad Etzel <c...@twitter.com> wrote: > Hi Sikora, > > Are you sure you are not manually specifying an oauth_callback > parameter (even if it is blank) when requesting the original tokens? > The oauth_verifier token (as seen in your sample URL) is only returned > when an oauth_callback is manually specified; otherwise it will use > the callback URL set in the application settings. > > Thanks, > -Chad > > On Fri, Aug 14, 2009 at 3:47 PM, Sikora<sik...@gmail.com> wrote: > > > Well I tried to find something related to my problem, no clue yet, so > > I need some help here. > > > After sending my user to the authentication URL and clicking on the > > Allow button twitter doesn't redirects the user to the previously > > registered callback URL. > > > Somehow it redirects to > >http://twitter.com/oauth/test?oauth_token=aYDJYgKTKqOGtm1t******HzqWU... > > > And this is the beautiful "that page doesn't exist" > > > So, am I doing something wrong or is there a bug out there? > > > Thanks.
