Ah yes, I have seen that "cookie". It is in the return URL but only for a split second. If you screen shot the window during that time, you should be able to see the code for the "cookie". I do not know why they call it a cookie though. Token would be a more appropriate and applicable term.
On Thu, Jul 23, 2009 at 11:44 PM, Ray Baxter <[email protected]> wrote: > The magic cookie for a calendar is not a http cookie. It's a part of a url > that provides access to a calendar. > Ray > > > On Thu, Jul 23, 2009 at 11:25 PM, Joey Kippen <[email protected]>wrote: > >> Actually, clear your cookie cache before you start. Do whatever steps you >> need to to activate the creation of the cookie. You should be able to find >> the cookie in the cache afterwork. You will need to open the cookie and read >> the necessary information. Hopefully it is not encrypted. I have not >> checked. Anyway, with the necessary information you should be able to call >> on it. I do not know how useful it would be but there you have it. >> >> On Thu, Jul 23, 2009 at 10:56 PM, Ray Baxter <[email protected]>wrote: >> >>> I don't think so. >>> >>> >>> On Wed, Jul 22, 2009 at 9:11 AM, chrisjshull <[email protected]>wrote: >>> >>>> >>>> How can I get the magic cookie for a calender? >>>> >>>> I'm using the php API and letting the user log in. But then I'd like >>>> to get the magic cookie for later use. >>>> >>>> Is that possible? >>>> >>>> >>>> >>> >>> >>> >> >> >> > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
