Comment 12 for bug 1103136

For the record, I don't think the Go library is wrong, it's just choking on the lack of gzip trailer which is chopped off by us incorrectly implementing the Range when gzip is present, not leaving enough room for the gzip trailer.

In other words, if you request a Range X-Y, we need to return (Y-X)-Z bytes + gzip trailer, but instead we're returning (Y-X) bytes and leaving the gzip trailer off, and Go is then correctly pointing out the 'unexpected EOF', although it seems to hide the fact that that error happens inside the gzip reader.