[twitter-dev] Re: 401 unauthorized
The https to http hack worked for me consistently for a while but now even this no longer works for my app. Can anyone else confirm this? On Mar 30, 8:10 am, Nick Spacek nick.spa...@gmail.com wrote: Sorry, what hack is that? I've heard a bunch of advice on working around this, but nothing conclusive. I believe he means changing fromhttps://api.twitter.comtohttp://api.twitter.com. I can confirm that this works for me as well. Obviously not ideal, but an interim solution? -- 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-dev] Re: 401 unauthorized
I can also confirm this behavior. Is it me or is everyone in here using .NET? Did I possibly miss somewhere that this is a .NET forum? I am also using a .NET library (Twitterizer). Wondering if anyone not using .NET is experiencing this issue? On Mar 23, 8:21 am, Craig Walls hab...@gmail.com wrote: 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
