tags:

views:

3459

answers:

4

Is anyone else having a difficult time getting Twitters oAuth's callback URL to hit their localhost development environment. Apparently it has been disabled recently. http://code.google.com/p/twitter-api/issues/detail?id=534#c1

Does anyone have a workaround. I don't really want to stop my development

+3  A: 

Yes, it was disabled because of the recent security issue that was found in OAuth. The only solution for now is to create two OAuth applications - one for production and one for development. In the development application you set your localhost callback URL instead of the live one.

arikfr
I just tried doing that, but it doesn't accept http://localhost:3000/ as a URL format...
David N. Welton
Yes, they seem to filter such URLs. :( But the support for custom callback urls is back - maybe they're supported there.
arikfr
+5  A: 

Here is the workaround: http://bit.ly/FZWVY

Best of luck!

Tony
+1  A: 

I just had to do this last week. Apparently localhost doesn't work but 127.0.0.1 does...go figure. This of course assumes that you are registering two apps with Twitter, one for your live www.mysite.com and another for 127.0.0.1

Adam
A: 

Use http://bit.ly/localhost

abraham

related questions