We have identified the issue and deployed a fix.  Please let us know
if you continue to see high error rates on oauth URLs.

  ---Mark

On Wed, Nov 11, 2009 at 3:54 PM, John Kalucki <jkalu...@gmail.com> wrote:
>
> We're looking into the 500s on oAuth requests.
>
>
> -John Kalucki
> http://twitter.com/jkalucki
> Services, Twitter Inc.
>
>
> On Nov 11, 3:39 pm, Sean <rag...@gmail.com> wrote:
>> Getting the same thing, 500's from access token requests.
>>
>> This is affecting all of our new users.
>>
>> Any insight would be lovely!
>>
>> Sean
>> Ping.fm
>>
>> On Nov 11, 12:29 pm, Yu-Shan Fung <ambivale...@gmail.com> wrote:
>>
>> > Hi All,
>>
>> > I've been getting a high number of 500 errors (about 50% of the time
>> > yesterday) after user authenticated via oauth, and I try to get the access
>> > token from twitter. The weird thing is that the error is not consistent, 
>> > and
>> > the exact same code/setup works about half the time, with the same test 
>> > user
>> > acocunt.
>>
>> > I'm using the ruby oauth gem and here's the error it returns
>> >  500 "Internal Server Error"
>> >  /usr/lib/ruby/1.8/net/http.rb:2097:in `error!'
>> >  [RAILS_ROOT]/vendor/gems/oauth-0.3.5/lib/oauth/consumer.rb:199:in
>> > `token_request'
>> >  [RAILS_ROOT]/vendor/gems/oauth-0.3.5/lib/oauth/tokens/request_token.rb:18:in
>> > `get_access_token'
>> > ....
>>
>> > Any idea what could be causing this?
>>
>> > Thanks, much appreciated!
>> > Yu-Shan
>>
>> > --
>> > “When nothing seems to help, I go look at a stonecutter hammering away at
>> > his rock perhaps a hundred times without as much as a crack showing in it.
>> > Yet at the hundred and first blow it will split in two, and I know it was
>> > not that blow that did it, but all that had gone before.” — Jacob Riis
>

Reply via email to