From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([209.51.188.92]:53519) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hNn2d-0000WK-Hh for guix-patches@gnu.org; Mon, 06 May 2019 19:29:04 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hNn2c-0005UI-FN for guix-patches@gnu.org; Mon, 06 May 2019 19:29:03 -0400 Received: from debbugs.gnu.org ([209.51.188.43]:44216) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1hNn2c-0005UC-CX for guix-patches@gnu.org; Mon, 06 May 2019 19:29:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1hNn2c-0001XV-4n for guix-patches@gnu.org; Mon, 06 May 2019 19:29:02 -0400 Subject: [bug#34807] [PATCH 1/2] Add (guix lzlib). Resent-Message-ID: From: Tobias Geerinckx-Rice References: <20190310180209.11578-1-mail@ambrevar.xyz> <8736ne3855.fsf@gnu.org> <87pnp2f7gr.fsf@ambrevar.xyz> <8736lxdxn6.fsf@ambrevar.xyz> <87lfzm7fdz.fsf@gnu.org> <878svm5xic.fsf@ambrevar.xyz> <87ef5e0vvv.fsf@gnu.org> <87o94h527a.fsf@ambrevar.xyz> <87a7fzffip.fsf@gnu.org> In-reply-to: <87a7fzffip.fsf@gnu.org> Date: Tue, 07 May 2019 01:28:09 +0200 Message-ID: <87v9ynf9iu.fsf@nckx> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-patches-bounces+kyle=kyleam.com@gnu.org Sender: "Guix-patches" To: Ludovic =?UTF-8?Q?Court=C3=A8s?= Cc: Pierre Neidhardt , 34807@debbugs.gnu.org --=-=-= Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable Ludo', Ludovic Court=C3=A8s wrote: > So, depending on the client, =E2=80=98guix publish=E2=80=99 should return= either=20 > a > narinfo-for-gzip or a narinfo-for-lzip. To make it possible,=20 > new > clients could send an extra HTTP header, say=20 > =E2=80=98X-Guix-Compression=E2=80=99, that > would specify their preferred compression method(s). =E2=80=98guix=20 > publish=E2=80=99 > would take that into account when replying. There's a standard[0] HTTP header for that: =E2=80=98Accept-Encoding=E2=80= =99. Unfortunately (and for reasons that I cannot fathom), it doesn't=20 use standard MIME types, but pseudostandard strings like =E2=80=98gzip=E2= =80=99=20 and =E2=80=98br=E2=80=99. We can boldly add =E2=80=98lzip=E2=80=99 to that= :-) Similarly, servers can send =E2=80=98Content-Encoding=E2=80=99[1] HTTP head= ers,=20 but I don't see a need for it here. Kind regards, T G-R [0]:=20 https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Accept-Encoding [1]:=20 https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Encoding --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iHUEARYKAB0WIQT12iAyS4c9C3o4dnINsP+IT1VteQUCXNDDCQAKCRANsP+IT1Vt efyOAPkBiYUZx40xk8eKEOJnDH2nvES6mx695c5hyWuKutqVcAEAiGbLbXrxylsN H/EkvEUOrKKkgjof1fH2zksp4TYwkgM= =MOcO -----END PGP SIGNATURE----- --=-=-=--