Re: [twitter-dev] oAuth and callback function
In general, I recommend explicitly specifying your oauth_callback on the request token step, whether you're doing out of band auth or doing standard OAuth flows. If performing out-of-band auth, provide oauth_callback=oob. While there's nothing wrong with relying on what you've stored in your application record, it's simply better (and spec compliant) OAuth to be explicit. Taylor On Wed, Jun 30, 2010 at 6:29 PM, Elhassan Rais wrote: > check the config.php file if you defined the callback url there. > > > On Wed, Jun 30, 2010 at 6:23 PM, EastSideDev wrote: > >> I changed the url for my callback function, and updated that >> information in my application settings on the twitter API site. The >> problem I am running into, is that I am still getting the old callback >> URL. Is there a lag time, before changes take effect? > > >
Re: [twitter-dev] oAuth and callback function
check the config.php file if you defined the callback url there. On Wed, Jun 30, 2010 at 6:23 PM, EastSideDev wrote: > I changed the url for my callback function, and updated that > information in my application settings on the twitter API site. The > problem I am running into, is that I am still getting the old callback > URL. Is there a lag time, before changes take effect?
Re: [twitter-dev] oAuth and callback function
I've only done PIN based authentication, but, my understanding of the protocol was that you supply the callback url in your oauth request token call? Are you seeing that you are getting the old callback after updating the code in the request token step? George On Wed, Jun 30, 2010 at 9:23 PM, EastSideDev wrote: > I changed the url for my callback function, and updated that > information in my application settings on the twitter API site. The > problem I am running into, is that I am still getting the old callback > URL. Is there a lag time, before changes take effect?
