You are deleting a resource and then requesting it. A response code of 410 Gone make senses to me. What am I missing, other than the secret to how or why you are deleting your main calendar?
Ray On Fri, Jul 31, 2009 at 7:03 AM, petteri <[email protected]> wrote: > > Hi, > > I'm now able to reproduce this problem. Here are the instructions: > > 1. Delete main calendar > 2. Full synchronize some stuff in (not sure is this really necessary) > 3. Request: > https://www.google.com/calendar/feeds/default/private/full?updated-min=2009-07-31&gsessionid=. > .. > -> DEFECT: Response: Error 410: "Gone" > > Note, today is 2009-07-31. > > BR, > Petteri > GoogaSync.com > > > On Jul 31, 4:43 pm, petteri <[email protected]> wrote: > > I'm also defining that use GData-Version 2.1, why these changes are > > affecting to my users? > > > > On Jul 31, 4:40 pm, petteri <[email protected]> wrote: > > > > > > > > > Hi, > > > > > I am getting reports from my users that they are getting 410 GONE even > > > though updated-min date is set properly? Can you elaborate more what > > > is actually changed? > > > > > BR, > > > Petteri > > > GoogaSync.com > > > > > On Jul 30, 8:12 pm, Trevor Johns <[email protected]> wrote: > > > > > > Hello everybody, > > > > We have a new Calendar Data API release for you all. The changelog is > > > > below. > > > > > > As always, you can subscribe to the Atom feed athttp:// > code.google.com/apis/calendar/changelog.htmltogetthe latest > > > > news on > > > > any future releases. > > > > > > Calendar Data API Release 2009-08 > > > > Date: July 29, 2009 > > > > Description: > > > > > > This release fixes the following issues: > > > > > > - Ensure that HTTP 410 (Gone) is returned if `updated-min` is set to > a > > > > date > > > > before the last time a calendar was cleaned. This allows sync > > > > clients to > > > > know that all events are out out of sync and that a complete > rebuild > > > > should > > > > be performed. (Requires protocol version 2.1.) > > > > - If both `gd:when` and `gd:recurrence` data are specified when > > > > creating an > > > > event entry, an HTTP 400 (Bad Request) error is returned. > > > > - Issue 866: Attempting to configure a calendar to use an invalid > > > > timezone now > > > > returns an HTTP 400 (Bad Request) error rather than defaulting to > > > > UTC. > > > > > > -- > > > > Trevor Johns > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
