In addition, the server time is returned in the HEAD of every response from the Twitter API. If the first request fails you can inspect the time returned in the HEAD and calculate the difference between it and your local time. You can then add/subtract that difference to the timestamp you use for OAuth requests.
Hope that helps, @themattharris Developer Advocate, Twitter http://twitter.com/themattharris On Fri, Nov 19, 2010 at 9:35 AM, M. Edward (Ed) Borasky < zn...@borasky-research.net> wrote: > The server administrators can and should sync server clocks automatically > to the world time clocks using Network Time Protocol (NTP). If your "IT > department" isn't doing this, find out why not. Most likely they don't know > it's possible. It's pretty easy on Linux and Windows, but you do need an > Internet connection to the outside world, so the firewall folks need to be > involved and you have to make sure your server-side NTP software is kept up > to date on security patches. > -- > M. Edward (Ed) Borasky > http://borasky-research.net http://twitter.com/znmeb > > "A mathematician is a device for turning coffee into theorems." - Paul > Erdos > > > > Quoting computerzworld <meat2...@gmail.com>: > > Thanks for your reply. Is there anyway to sync server clock >> programatically? Or any other way by which we can make the stuff >> working? Because I don't have access to server hardware. >> >> On Nov 12, 12:28 am, Abraham Williams <4bra...@gmail.com> wrote: >> >>> Your servers clock needs to be properly synced using NTP. >>> >>> http://en.wikipedia.org/wiki/Network_Time_Protocol >>> >>> Abraham >>> ------------- >>> Abraham Williams | Hacker Advocate | abrah.am >>> @abraham <https://twitter.com/abraham> | github.com/abraham | >>> blog.abrah.am >>> This email is: [ ] shareable [x] ask first [ ] private. >>> >>> On Thu, Nov 11, 2010 at 05:36, computerzworld <meat2...@gmail.com> >>> wrote: >>> > Hello, >>> > I am using Twitter Oauth library for signing in to Twitter >>> > & getting access token for posting tweets programatically. But when I >>> > am trying to run the application on my server it is giving me error >>> > like >>> >>> > "Failed to validate oauth signature and token" >>> >>> > I tried to move the application on another server & it is working. So >>> > what should be the problem behind this? Is there any configuration >>> > required for the server in order to make this work? Please help me. >>> >>> > Thanks in advance. >>> >>> > -- >>> > 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 >>> >> >> -- >> 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 >> >> > > -- > 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 > -- 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
