/oauth/request_token sporadically not returning a request token?


Starting yesterday evening, we’ve noticed a small number of calls to /oauth/request/token which return without a valid request token. I can’t reproduce this right now since it seems to happen pretty sporadically. Are there any known issues with this endpoint? Will try to update with more details if I can reproduce it.

Update: Resolved - See my response to @chriscdn below.


I’ve started seeing this as well as of two days ago. I can’t determine what the pattern is, but sometimes it returns a token and sometimes a blank string.


We saw almost no instances of this for 2 weeks, then hundreds of failed requests in the past few days. Anyone know what’s going on?


Yeah we have had the same issue last two days. Code was working, then started failing intermittently, now seems to barely ever work. Has been a real bummer for a product we are launching.


80% fail rate, what’s going on…

About to connect() to api.twitter.com port 443 (#0)

  • Trying… connected
  • Connected to api.twitter.com ( port 443 (#0)
  • CAfile: /etc/pki/tls/certs/ca-bundle.crt
    CApath: none
  • NSS error -5938
  • Closing connection #0
  • SSL connect error
    curl: (35) SSL connect error


We are getting blank responses with status: 404. They seem happen for several hours then it will work fine for a few hours, then 404s again.


Is this related to https://dev.twitter.com/discussions/1549?


This is unlikely related. There are cases where a user’s information cannot be fetched through the internal processes that happen during this sequence – these should be few and far between. It’s a difficult problem to track down as repeatable examples are hard to come by – usually when we get a specific user id that has this issue, it’s resolved by the time it can be looked at.

That said, I’ll continue informing the engineering team that these continue happening.


This SSL issue should now be resolved.


Seeing this quite a bit more over the last 2-3 days. This morning it is repeatable almost constantly for my account.


Thanks for the report, @xsnrg! What’s the exact URL you’re executing when you see this? What’s your source IP address? Can you share a trace of the request that includes the HTTP headers you received in response?


Hi Taylor,

We’re seeing 404 responses when hitting https://api.twitter.com/oauth/request_token:

Date: Tue, 13 Sep 2011 17:09:00 UTC
Server: tfe


Can you share the consumer key as well? Thanks! Also, if it is possible, can you try using http instead of https on the request_token step temporarily and see if that decreases this happenstance?


Hi Taylor,

I’m still seeing 404s after switching off SSL for the request step, a few more successes, and occasional 401s (looking into it). Let me know how I can be more useful in getting to the bottom of this:


Seeing this pop up again today. Anyone else seeing issues with the request_token step?


Can you share the HTTP headers you’re getting in the response? Do you have a time you can pinpoint that it started for you? When did it stop before?

Thanks David!


Hey Taylor,

Sorry - for some reason I wasn’t getting email updates on this issue. Started getting 404s sporadically last night - don’t have an exact time recorded, but since this morning, it looks like pretty much every request returns a 404:

Date: Wed, 28 Sep 2011 17:31:04 UTC Server: tfe


I’m still getting sporadic 404 errors with my Django application, which makes the https://twitter.com/oauth/request_token request using httplib.HTTPSConnection. The response header echos what @dtran320 is getting with:

Date: Wed, 28 Sep 2011 17:58:02 UTC
Server: tfe

If I put the exact same URL in my browser then it works.


Sorry about this problem popping up again…

Can you both share with me the User-Agent you’re setting for your request and the IP address(es) you’re using to connect? Feel free to email me at episod@twitter.com if you would rather.



Email sent. Thanks for looking into this Taylor!