If you're experiencing this issue, can you please provide these additional details: * are the OAuth URLs you are using http or https? * do your OAuth URLs contain the api subdomain? (you really should be if you aren't) * what OAuth library (if any) are you using to sign your requests? * If you're observing the response HTTP headers on failed requests, what server time is presented in the "Date" HTTP header? What is your OAuth timestamp?
Thanks! @episod <http://twitter.com/episod> - Taylor Singletary - Twitter Developer Advocate On Mon, Mar 21, 2011 at 6:24 AM, Taylor Singletary < taylorsinglet...@twitter.com> wrote: > Thanks everyone for the detailed information in these reports; they'll help > a lot while we track down the issue. Will update this thread when we know > more. > > @episod <http://twitter.com/episod> - Taylor Singletary - Twitter > Developer Advocate > > > > On Mon, Mar 21, 2011 at 6:03 AM, Tatham Oddie <tat...@oddie.com.au> wrote: > >> Please go and star this issue: >> http://code.google.com/p/twitter-api/issues/detail?id=2118 >> >> On Mar 19, 11:47 pm, Trevor Dean <trevord...@gmail.com> wrote: >> > Is anyone else experiencing any 401 errors all of a sudden? I was doing >> > some testing this morning and was logging in fine using twitter and then >> 10 >> > min later I started getting 401 unauthorized errors. >> > >> > Thanks, >> > >> > Trevor >> >> -- >> 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
