Hi Andrey, We have a bug right now with oauth_callbacks with non-standard URI schemes -- hope to have it fixed soon.
Taylor On Tue, May 18, 2010 at 9:04 PM, Andrey Vyrvich <andry.virv...@gmail.com>wrote: > I've make a request like > > http://twitter.com/oauth/request_token?oauth_callback=chrome%3A%2F%2Fid_twitter%2Fcontent%2Ftwitter_oauth.html%3FTwitterExOAuthcallback%3Dtrue&oauth_consumer_key=3H.. > .. > > where > > oauth_callback=chrome://id_twitter/content/twitter_oauth.html? > TwitterExOAuthcallback=true > > but when authorization complete 'http://twitter.com/oauth/authorize' > trying to redirect to > > > chrome:///content/twitter_oauth.html?TwitterExOAuthcallback=true&oauth_token=5Pln9.... > <meta http-equiv="refresh" content="0;url=chrome:///content/ > twitter_oauth.html?TwitterExOAuthcallback=true&oauth_token=5Pln9..."> > > so, id_twitter were lost somewhere > please advise >
