Hello David,
After going through numerous codes and oAuth mechanisms several times,
i would like to ask you, does my website, google's server and user
being geographically in different places causing this error?
I think there might be some user data redundancy is caused in these
moments which is causing google's server to reject token. If above
cause is true then as far as i can guess, this is actually caused by
delay between requests due to geographical dispersion. Currently i
cannot think of any quick patch on this rather than just adding some
delay between repetitive requests to obtain access token. Still this
will fail 70% times.
You asked for my ip on 21st Sep. Did you get anything from it?
Thanks alot for all your time and concern. I strongly appreciate it.
Cheers!
P.S. If the problem i mentioned above is true then does google already
working on it? how long can we expect to get this issue fixed? Cheers!
Aditya Hajare
On Sep 16, 12:04 am, David Primmer <
prim...@google.com> wrote:
> Hi again,
>
> I've tried those URLs a few times and I can't seem to reproduce your
> issue. Are you doing anything odd like doing lots of these same
> requests very quickly? Or maybe doing lots of grants with no revokes?
> If you see the issue again, please respond quickly and we might be
> able to catch it in our logs.
>
> davep
>
>
>
>
>
>
>
> On Wed, Sep 14, 2011 at 10:05 PM, Aditya Hajare <
adity...@gmail.com> wrote:
> > Hello David,
> > This is the url in approval page addressbar when 500 is encountered :
> >
https://accounts.google.com/o/oauth2/auth?scope=https://www.google.co...
>
> > This is the url in approval page addressbar when everything is working
> > fine :
> >
https://accounts.google.com/o/oauth2/auth?scope=https://www.google.co...