The oauth_timestamp has no time zone; it's implicitly Universal Time (also known as GMT). But OAuth service providers usually require consumers' clocks to be fairly accurate.
You could try implementing your client to adapt to the server's clock. It could look at the Date in the HTTP response headers, or the oauth_acceptable_timestamps in the response body. On Feb 21, 7:38 am, Mark <mar...@gmail.com> wrote: > Hi Vinod, I don't understand this though - the PC requesting the oauth > service is just a regular user - I can't expect them to have their > timezone set to be the same as the server? The server is using eastern > standard time. There must be some way around this issue, otherwise all > oauth services would require their client clocks to also be in EST? > For example, I can make my timezone anything and it still works with > twitter oauth services - so is the twitter service just ignoring this > timestamp restriction? -- You received this message because you are subscribed to the Google Groups "OAuth" group. To post to this group, send email to oa...@googlegroups.com. To unsubscribe from this group, send email to oauth+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/oauth?hl=en.
