Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to get token due to timezone #2

Closed
deeperror opened this issue Sep 24, 2009 · 5 comments
Closed

Unable to get token due to timezone #2

deeperror opened this issue Sep 24, 2009 · 5 comments

Comments

@deeperror
Copy link

This would not return a token until I updated the timezone on my server to match the twitter server GMT which is what twitters date was set to in the CURL responses along with a 401 "Failed to validate oauth signature and token"

Reference: http://groups.google.com/group/twitter-development-talk/browse_thread/thread/aadee92bc5c34f29?pli=1

@abraham
Copy link
Owner

abraham commented Sep 24, 2009

I'll add this to the documentation but it is really not something this library should fix.

@deeperror
Copy link
Author

So in order for this library to work as expected the servers time zone has to be GMT?

@abraham
Copy link
Owner

abraham commented Sep 24, 2009

The OAuth Spec requires the timestamp be in GMT. I will explore adding a setter for the timestamp though.

@paularmstrong
Copy link

use gmdate('U') to get the current GMT time.

@shadowhand
Copy link

Using time() returns the UNIX timestamp, which is always GMT.

@abraham abraham closed this as completed Aug 9, 2014
@prandam prandam mentioned this issue Jul 26, 2016
Repository owner locked and limited conversation to collaborators Dec 30, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants