git/list[1] front-page[2] threads[3] people[4] search[5] about
 

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

From
Shawn Pearce <spearce@spearce.org>
Date
Sep 20, 2012, 02:59 UTC
Message-ID
<CAJo=hJtUOQK8iYXa3zMm2c5NEF-6s=v4MHYWhxADohKmRrqe9Q@mail.gmail.com>
In-Reply-To
<7vtxutcymr.fsf@alter.siamese.dyndns.org>
On Wed, Sep 19, 2012 at 5:43 PM, Junio C Hamano <gitster@pobox.com> wrote:
Show 5 quoted lines
>> -> 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--

Previous: Junio C Hamano
Message 3 of 3 in “Enable info/refs gzip decompression in HTTP client”
  1. Enable info/refs gzip decompression in HTTP clientShawn O. Pearce, Sep 19, 2012
  2. Junio C HamanoSep 20, 2012
  3. Shawn PearceSep 20, 2012

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.