[oauth] Re: Trouble with the javascript library and timestamps (possible fix)
Ahh, so is that the most up-to-date oauth js library? Wonder how I grabbed the wrong one... Nice work btw, very similar approach to tackle the problem too! Good to hear that your at LinkedIn, tis a great site that I need to use more often :-S On Sep 11, 1:03 am, John Kristian jmkrist...@gmail.com wrote: Thank you, David! A great idea, and a working implementation too. I committed a similar change tohttp://oauth.googlecode.com/svn/code/javascript/oauth.js It uses the query string parameter name oauth_timestamp, instead of servertime. For example, in PHP: script src=js/oauth.js?oauth_timestamp=?=time()? Can you say more about how you're using this? I'm pleasantly surprised to hear it's useful, since browsers don't allow cross-site scripting. By the way, Netflix no longer maintains this code (as far as I know). I wrote it, and maintain it in my spare time, but I work at LinkedIn now. On Sep 9, 10:50 am, David King da...@1daylater.com wrote: OK, I have created a simple fix that works in the manner I've explained. -- How to use -- script src=/js/oauth.js?servertime=1252518585 --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups OAuth group. To post to this group, send email to oauth@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 -~--~~~~--~~--~--~---
[oauth] Re: Trouble with the javascript library and timestamps (possible fix)
Thank you, David! A great idea, and a working implementation too. I committed a similar change to http://oauth.googlecode.com/svn/code/javascript/oauth.js It uses the query string parameter name oauth_timestamp, instead of servertime. For example, in PHP: script src=js/oauth.js?oauth_timestamp=?=time()? Can you say more about how you're using this? I'm pleasantly surprised to hear it's useful, since browsers don't allow cross-site scripting. By the way, Netflix no longer maintains this code (as far as I know). I wrote it, and maintain it in my spare time, but I work at LinkedIn now. On Sep 9, 10:50 am, David King da...@1daylater.com wrote: OK, I have created a simple fix that works in the manner I've explained. -- How to use -- script src=/js/oauth.js?servertime=1252518585 --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups OAuth group. To post to this group, send email to oauth@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 -~--~~~~--~~--~--~---
[oauth] Re: Trouble with the javascript library and timestamps (possible fix)
OK, I have created a simple fix that works in the manner I've explained. It doesn't adhere to the OAuth namespace, it's probably best that the author integrates it in the manner that sticks to their style of coding. -- How to use -- Download the new file here: http://dl.getdropbox.com/u/1858499/oauth.js Now, when you link to it, include the timestamp in the src parameter for the script element like so: script type=text/javascript src=/js/oauth.js? servertime=1252518585/script Et viola, no more timestamp mismatches, regardless of the users setup! --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups OAuth group. To post to this group, send email to oauth@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 -~--~~~~--~~--~--~---
