yamano is right. The feed with the free-busy permission seems inaccessible for the permitted (other) users if without the magic-cookie. A client application with the authentication header of the permitted user trying to access the feed keeps getting 404 Not Found at least as of now. It does not depends on API libraries and is assumed as a backend side problem.
For example: * User_A has set a free-busy permission of his calendar to User_B. * The feed of the User_B's calendar list now contains the free-busy only feed URL of User_A's calendar (i.e. http://www.google.com/calendar/feeds/User_A/private/free-busy) * When a client application which has had the authentication header of User_B tries to access this URL, it receives 404 Not Found. * Once User_A changes the permission to others such as read, the feed becomes accessible for User_B. This can be easily reproduced with a web browser when login as User_B and open the feed URL. If the permission is fee-busy, the web browser displays 404. If others, it displays the feed. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
