Alain, We are using gzip compression for calendar requests and when we receive a response that indicates a failure and gzip is noted in the response header we run this through the GZipStream class to parse the response. We've beend doing this for years to address a problem where the details of the failure is otherwise shown as uncompressed. In this case we are reading the header response, we notice the reponse is encoded as gzip and we then read the stream into the GZipStream class to deflate the response. It's this case the response stream could not be read likly because it was closed or missing data. Here is the specific stack trace which includes our modification to unzip the response stream. Otherwise, the response contains the raw uncompressed response which is not readable. at System.IO.Compression.GZipStream..ctor(Stream stream, CompressionMode mode) at Google.GData.Client.GDataRequestException.ReadResponseString() at Google.GData.Client.GDataRequestException.get_ResponseString() I don't believe this issue is directly related to the GZip funtion since the failure is occuring when reading the response stream which appears to have resuled from a Google calendar service failure. Again, it is important (I think) to note that we've been using this approach for years without any problems and then recently users are randomly seeing this error appear. If they run the request again it typically goes away. Do you have a change log or something that details all the changes made to the Google calendar service and/or hosting environment so we (developers) can help troubleshoot these issues?
-- 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
