Hi David, When was your most recent report of this behavior? As you may have seen on our status blog, we temporarily took user signups/profile updating down for a period this morning, and a side effect of that were some temporary issues with OAuth (aside from some of the other transient issues that have arisen lately).
Please note also that without the api subdomain, this OAuth authorization path is out-dated -- you'll be happier in the long run by changing your OAuth paths to api.twitter.com/oauth/* @episod <http://twitter.com/episod> - Taylor Singletary - Twitter Developer Advocate On Tue, Mar 1, 2011 at 1:22 PM, David <[email protected]> wrote: > Hi Taylor, > > We have users reporting that https://twitter.com/oauth/authorize?<oauth > params> just returns an empty response (324 in chrome net:: > ERR_EMPTY_RESPONSE), so it seems like it's timing out. Obviously, this never > makes it back to our callback, so what should we do as an application in > this case? > > David > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: > http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk > -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
