I have tried the same browser test (navigating to the feed page manually with the query) for the weather calendar as I had previously done for our personal calendars and it throws the same error:
http://www.google.com/calendar/feeds/#pweather%40group.v.calendar.google.com/public/full/ Invalid request URI. Removing the #p prefix from the username yields: [com.google.calendar.server.impl.css2.LookupUserLazyLoadPrincipal email:'[EMAIL PROTECTED]'] does not allow feeds I dont know if this helps at all, but after having played with the url a bit, it seems the problem definitely lies in the assigned username for this calendar. Sebastian On Jan 5, 4:31 pm, "[EMAIL PROTECTED]" <[EMAIL PROTECTED] lange.net> wrote: > Sebastian and I have been referring to the gcalci code in our code, > which is a mashup of calendar data and Timeline (http://simile.mit.edu/ > timeline/). > > Following Eric's pointer, I can confirm that it is the weather > calendar that is also causing up problems. I've disabled getting this > calendar for the moment, but it suggests an inconsistency in the API. > > Rory --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
