request_token 401 error: possibly due to daylight savings?


#1

Hello,

We’ve been having problems with users attempting to use twitter login for one of our websites since the week of the 8th of March, 2015.

The request we are sending has been working for some time but suddenly stopped working the week of the 8th, which led us to believe there may be some daylight savings related problem.

However, we have tried everything possible to correct this issue by adjusting server time and nothing has worked so far. We have also verified that our consumer_key and consumer_secret tokens are valid and matching the ones issued to us. Nothing to do with this code has been changed since around 2012, and it has been working since then, so we are at a loss as to what the issue may be.

Our servers are located in Japan and I’m not sure if other users from this region have been experiencing similar problems.

Here is a sample of the api requests that have been failing:


https://api.twitter.com/oauth/request_token

oauth_consumer_key=XXX
oauth_signature_method=HMACSHA1
oauth_timestamp=1427680425
oauth_nonce=8584556
oauth_version=1.0
oauth_callback=www.xxx.com/mycallbackpage.aspx
oauth_signature=YYY

Any help would be greatly appreciated.

Cheers,
Eric