Hi Charlie and Derek, Thank you both very much for the report. I recreated this and filed a bug for the issue.
Cheers, -Ryan On Dec 11, 7:03 am, "Charlie Wood" <[EMAIL PROTECTED]> wrote: > I've run into what I think is a bug, and I've been able to verify the > behavior manually using curl and straight HTTP operations against the > API. Here's what happens: > > 1. User A creates a calendar and shares freebusy data with User B. > 2. User A can access the freebusy projection of the calendar via the > API. > 3. User B can see the freebusy projection fine in Google Calendar. > 4. The freebusy projection of User A's calendar is listed in User B's > metafeed. > > So far so good, but here's the problem: > > 5. When user B tries to access the freebusy projection of User A's > calendar via the API (by making an authenticated request to the URL > listed in his metafeed with a session id attached) he gets a 404 error > with the body "Cannot access the calendar you requested" (embedded in a > bunch of HTML) > > Am I doing something wrong, or is this a bug? > > 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 -~----------~----~----~----~------~----~------~--~---
