The subject line says it all. My Google Calendar Interface has started blowing up, and I've determined that it's happening because the C time() function (which is used in generation of the digital signature for the web service request) is now returning a time number that is one hour in the future. And the Google Calendar web services are rejecting it.

If I run the request out of OAuth Playground, the time number is 3600 seconds earlier than what I get on the 400, and if, in the debugger, I manually subtract 3600 seconds from the time number, it works just fine, which makes the above diagnosis look pretty conclusive.


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2021 by and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.