I've just confirmed what Gary M says...switching to HTTP does seem to make it work. But HTTPS requires a >15 second delay between obtaining a request token and exchanging it for an access token.
On Mar 23, 1:48 am, Gary M <gen...@gmail.com> wrote: > Correction. Switching to HTTP does remove the issue, so I'm making that a > configurable setting in our app as a temporary workaround. -- 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