I'm seeing intermittent issues as well on the /oauth/access_token endpoint. Have you ever gotten to the bottom of this or is it just best to handle the error and retry? Below is a capture of my HTTP requests:
POST /oauth/access_token HTTP/1.1 Authorization: OAuth oauth_signature="Thb80hXw6LKjiz1h8MFrNewp0KQ%3D", oauth_version="1.0", oauth_nonce="1474364130", oauth_signature_method="HMAC-SHA1", oauth_consumer_key="...", oauth_token="F2nCVegyxBKNa3TwjsoHolet5Env6ZvzV37xhQkmM", oauth_verifier="REGEX_FAILED", oauth_timestamp="1297355206" User-Agent: Java/1.6.0_22 Host: api.twitter.com Accept: text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2 Content-type: application/x-www-form-urlencoded Content-Length: 0 HTTP/1.1 401 Unauthorized Date: Thu, 10 Feb 2011 16:26:46 GMT Server: hi Status: 401 Unauthorized X-Transaction: 1297355206-55942-36174 Last-Modified: Thu, 10 Feb 2011 16:26:46 GMT X-Runtime: 0.00838 Content-Type: text/html; charset=utf-8 Content-Length: 1 Pragma: no-cache X-Revision: DEV Expires: Tue, 31 Mar 1981 05:00:00 GMT Cache-Control: no-cache, no-store, must-revalidate, pre-check=0, post-check=0 Set-Cookie: k=64.134.151.133.1297355206199446; path=/; expires=Thu, 17-Feb-11 16:26:46 GMT; domain=.twitter.com Set-Cookie: guest_id=129735520622032993; path=/; expires=Sat, 12 Mar 2011 16:26:46 GMT Set-Cookie: _twitter_sess=BAh7CDoPY3JlYXRlZF9hdGwrCE5uZRAuAToHaWQiJTUxZDA2OTQxYjBjYTM2%250AZjg2YzQwOGM2MjgxOWM0MjRkIgpmbGFzaElDOidBY3Rpb25Db250cm9sbGVy%250AOjpGbGFzaDo6Rmxhc2hIYXNoewAGOgpAdXNlZHsA--35de5076b33181311e1eec89909ae50eb393d70f; domain=.twitter.com; path=/; HttpOnly Vary: Accept-Encoding Connection: close -- 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
