Alain, THANK YOU for your attention to this issue. The redirect is the results of a call to Update() an entry https://www.google.com/googlecalendar/unavailable.html but I also believe that we are getting a similar response when performing a query. When then query happens and a redirect is returned this filters its way back through the .Net client API's which then tries to get the failure response from the stream which does not exist and this causes the stream is not readable. So, the root issue I think is that the calendar service is kicking back redirects related to the calendar not being available and depending on the operation (query, update, insert) the .Net client libraries are reacting differently. So, I think the Gzip compression issue was a sideeffect and not related to the _root_ issue which is why the calendar service is returning a redirect response. Note the frequency of this issue has increased dramatically within the past two months. Before that we have very few occurrences of this issue and we are using retry logic. thanks again. dave.
-- 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
