On 1/9/14, 4:26 PM, Ben Reser wrote: > What's happening is your httpd server is configured to add the gzip encoding > to > the headers of files being served that have filenames that end in .gz. > > Typically you'll see that setup on the server with something like this: > AddEncoding x-gzip .gz > AddEncoding x-compress .Z > > AddEncoding is part of mod_mime and is documented here: > https://httpd.apache.org/docs/current/mod/mod_mime.html#addencoding > > Those sorts of configurations should never apply to the Location being used to > serve Subversion.
Realized after sending I may not have been as clear as I should have been. AddEncoding inserts a Content-Encoding header that specifies that the file is gziped without changing the content of the body. The Subversion client decompresses the file but then realizes that it doesn't match the checksum it expected and issues an error. The purpose of the configuration option is to store pre-compressed files on disk that are served to clients that can support gzip Content-Encoding without needing to do the compression in real time while the client decompresses the content on its end and uses it seamlessly.
