We've got one user who gets it every time. I'll email you his info. -c
Lane LiaBraaten (Google) wrote: > Hi Charlie, > > Have you been able to reproduce this? If it's really just a couple > times out of millions I'd say it's just a hiccup and you should > retry. If you can come up with some parameters to reproduce, then the > source of the issue may become more apparent. > > Cheers, > Lane > > On Sep 7, 6:47 am, cwood <[EMAIL PROTECTED]> wrote: > > We've seen this only a couple of times (using code that has worked > > millions of times) and are looking for guidance on how to respond: > > > > * A user successfully authenticates using ClientLogin (meaning we get > > an HTTP 200 response after we > > callhttps://www.google.com/accounts/ClientLogin > > with the proper fields and headers set) > > * We parse the auth token out of the body of the response > > * We make a second call > > (tohttp://www.google.com/calendar/feeds/default/private/full) > > and include the auth token in the Authorization header > > * The response is an HTTP 401 ("token invalid") > > > > At that point, should we just do the ClientLogin call again to get a > > new auth token? If so, what's a reasonable number of retries? If not, > > what should we do at that point? > > > > Thanks, > > Charlie --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Data API" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/google-help-dataapi?hl=en -~----------~----~----~----~------~----~------~--~---
