Twitter oAuth callbackUrl - localhost development

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

Alternative 1.

Set up your .hosts (Windows) or etc/hosts file to point a live domain to your localhost IP. such as:

127.0.0.1 xyz.com

where xyz.com is your real domain.

Alternative 2.

Also, the article gives the tip to alternatively use a URL shortener service. Shorten your local URL and provide the result as callback.

Alternative 3.

Furthermore, it seems that it works to provide for example http://127.0.0.1:8080 as callback to Twitter, instead of http://localhost:8080.

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.

Just put http://127.0.0.1:xxxx/ as the callback url, where xxxx is the port for your framework

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.

Callback URL edited

http://localhost:8585/logintwitter.aspx

Convert to

http://127.0.0.1:8585/logintwitter.aspx