From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: "musl" gzip-compressed tarballs are decompressed if using newest wegt release
Date: Wed, 1 Nov 2017 11:26:04 -0400 [thread overview]
Message-ID: <20171101152604.GG1627@brightrain.aerifal.cx> (raw)
In-Reply-To: <alpine.LSU.2.20.1711011051060.6924@schiller.site>
On Wed, Nov 01, 2017 at 11:19:30AM +0100, Jens Schleusener wrote:
> Hi,
>
> not a real "musl" software problem but just an observation of a
> changed behaviour of "musl" tarball downloads with the newest "wegt"
> release (1.19.2): The tarballs are saved now decompressed but
> contains the original extension (.tar.gz). Although if the extension
> would be .tar it seems at least to me an undesired behaviour.
>
> Reason seems a new "wget" feature, here some extracted lines taken
> from the ChangeLog
>
> 2017-08-04
> Add gzip Content-Encoding decompression
> (gethttp): Decompress files with gzip Content-Encoding
>
> in combination with the HTTP header the www.musl-libc.org server delivers:
>
> Content-Type: application/x-tar
> Content-Encoding: gzip
>
> Solutions/workarounds may be on the server side delivering of a HTTP
> header like
>
> Content-Type: application/x-gzip
> (or Content-Type: application/octet-stream)
>
> or on the client side the use of the new "wget" option
>
> --compression=none
IMO this is both a bug in the server and a major regression in wget,
since lots of servers have this bug. I'll look at fixing it on my side
but I think it should be reported to wget and reverted since this is
going to break a *huge* number of build scripts that download tarballs
from affected servers.
Rich
next prev parent reply other threads:[~2017-11-01 15:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-01 10:19 Jens Schleusener
2017-11-01 15:26 ` Rich Felker [this message]
2017-11-01 15:50 ` Jens Schleusener
2017-11-01 18:08 ` Rich Felker
2017-11-01 19:09 ` Matias Fonzo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171101152604.GG1627@brightrain.aerifal.cx \
--to=dalias@libc.org \
--cc=musl@lists.openwall.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).