You can't access it from JavaScript in most use-cases unfortunately. It's why having both expires_in and expires_at would be nice.
On 23 déc. 2010, at 11:36, "Pelle Wessman" <pe...@kodfabrik.se<mailto:pe...@kodfabrik.se>> wrote: For the Web Server flow you will have a HTTP Date header containing the timestamp at which the token was generated - right? Combining the value of that header with expires_in will get you the value of expires_at. / Pelle On Tue, Dec 14, 2010 at 10:14 PM, Paul Walker <<mailto:pjwal...@gmail.com>pjwal...@gmail.com<mailto:pjwal...@gmail.com>> wrote: Has there been discussion of using expires_at as an exact epoch time in seconds as opposed to expires_in which is, at best, an approximation "from the time the response was generated by the authorization server?" I apologize if this has been discussed previously. ~pj _______________________________________________ OAuth mailing list <mailto:OAuth@ietf.org>OAuth@ietf.org<mailto:OAuth@ietf.org> <https://www.ietf.org/mailman/listinfo/oauth>https://www.ietf.org/mailman/listinfo/oauth _______________________________________________ OAuth mailing list OAuth@ietf.org<mailto:OAuth@ietf.org> https://www.ietf.org/mailman/listinfo/oauth
_______________________________________________ OAuth mailing list OAuth@ietf.org https://www.ietf.org/mailman/listinfo/oauth
