In theory, either way should work. I do remember seeing posts in this group where the gsessionid didn't work & switching to the S cookie did work.
On May 7, 8:59 am, Charlie Wood <[EMAIL PROTECTED]> wrote: > >From the documentation about creating an event: > > The response may also include a S cookie, which you > > should store and send this cookie with future requests > > as appropriate. Please see the knowledge base for > > more information on handling sessions with the > > Calendar data API. Please note: if a session ID > > indicated in a cookie header conflicts with the session > > ID passed as a gsessionid URL parameter, you will > > get caught in a redirect loop. > > I don't remember reading this before. Is it new? My code recognizes > the 302 Redirect resonse, parses out the gsessionid from the Location, > and retries the request with the new gessionid, but I'm seeing cases > where it apparently gets caught in a redirect loop. Should I be using > the 'S' cookie instead? In addition? > > Thanks, > Charlie --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Calendar 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-calendar-help-dataapi?hl=en -~----------~----~----~----~------~----~------~--~---
