Hello, Are you using a specific client library? Also, I would suggest using SSL (https) over non-SSL (http) whenever possible.
Best, Alain On Wed, Jun 8, 2011 at 3:25 AM, Charlie Wood <[email protected]> wrote: > *This is a really serious problem for us, and is affecting a lot of our > customers.* > > About 24 hours ago, many of our users started reporting a problem where > Google is returning > > HTTP 400 > Premature end of file > > in response to an authenticated (via ClientLogin) GET request to > > http://www.google.com/calendar/feeds/default/private/full > > The problem affects some accounts consistently, some sporadically, and > some, apparently, not at all. I'd be happy to provide a few of the > consistently-affected account names via email. > > Any help would be greatly appreciated. > > Thanks, > Charlie > Spanning Sync > > -- > 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://code.google.com/apis/calendar/community/forum.html > -- Alain Vongsouvanh -- 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://code.google.com/apis/calendar/community/forum.html
