Re: [PATCH] Enable info/refs gzip decompression in HTTP client

"Shawn O. Pearce" [off-list ref] writes:

From: "Shawn O. Pearce" <redacted>

Some HTTP servers try to use gzip compression on the /info/refs
request to save transfer bandwidth. Repositories with many tags
may find the /info/refs request can be gzipped to be 50% of the
original size due to the few but often repeated bytes used (hex
SHA-1 and commonly digits in tag names).

For most HTTP requests enable "Accept-Encoding: gzip" ensuring
the /info/refs payload can use this encoding format.

Disable the Accept-Encoding header on probe RPCs as response bodies
are supposed to be exactly 4 bytes long, "0000". The HTTP headers
requesting and indicating compression use more space than the data
transferred in the body.

All of the above sounds very convincing, but ...

... was loss of "deflate" intended?  If so why?  Could you explain
it in the log message?

 > Content-Type: application/x-git-upload-pack-request
 > Accept: application/x-git-upload-pack-result
 > Content-Length: xxx

On Wed, Sep 19, 2012 at 5:43 PM, Junio C Hamano [off-list ref] wrote:

quoted

-> Accept-Encoding: deflate, gzip
+> Accept-Encoding: gzip

... was loss of "deflate" intended?  If so why?  Could you explain
it in the log message?

Yes. I would add the following to the end of the commit message as a
new paragraph, please amend this for me:

--8<--
Only request gzip encoding from servers. Although deflate is
supported by libcurl, most servers have standardized on gzip
encoding for compression as that is what most browsers support.
Asking for deflate increases request sizes by a few bytes, but
is unlikely to ever be used by a server.
-->8--