Hi James, Thanks very much. I'll work on getting that information into the Developer's Guide ASAP.
Meanwhile, everything about how sessions are handled in calendar is accessible from the Knowledge Base: http://code.google.com/support/bin/answer.py?answer=55833&topic=10360 You really only need to handle either the cookie or the gsessionid URL param. If following the HTTP spec with regards to redirects and cookie handling, you'll end up using both for some requests, but most requests (ones that arent redirected) will end up using only the cookie. The only case where I've seen redirects as you describe was the result of sending conflicting values -- IE a request was sent with a cookie specifying a session id of ABC, but the gsessionid URL param specified a value of DEF (for instance). There was a bug in the cookie handling of the Java client library which caused this type of redirect loop if the session ID was changed (primarily due to requesting a calendar meta-feed)-- it has since been resolved. If the case you found is different, please let me know and we'll work on resolving it. Thanks, -Ryan On 3/1/07, James H. <[EMAIL PROTECTED]> wrote: > > > I'm working on some Ruby code to do Calendar stuff. I ran into an > issue where I'm getting an infinite loop of 302 redirects. > > I was redirecting to the "location:" header per the documentation, but > it just kept coming back with another 302 with a new gsessionid each > time. The Developer's Guide indicates adding the gsessionid is all > that's needed. I'm finding that's not the case. > > Digging through the discussion forums here, I found a developer > comment mentioning something about a cookie. After I added the cookie > info to the new GET request all was well. > > I'd recommend updating the Developer's Guide to mention the cookie. > The following 3 sections all mention the 302 redirect, but don't say a > thing about the cookie: > "Request the feed" > "Add an event" > "Send a date-range query" > > Regards, > James H. > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
