Mdthbs

This is a repost of my answer to a similar question:

The ZIP file format includes a directory (index) at the end of the archive. This directory says where, within the archive each file is located and thus allows for quick, random access, without reading the entire archive.

This would appear to pose a problem when attempting to read a ZIP archive through a pipe, in that the index is not accessed until the very end and so individual members cannot be correctly extracted until after the file has been entirely read and is no longer available. As such it appears unsurprising that most ZIP decompressors simply fail when the archive is supplied through a pipe.

The directory at the end of the archive is not the only location where file meta information is stored in the archive. In addition, individual entries also include this information in a local file header, for redundancy purposes.

Although not every ZIP decompressor will use local file headers when the index is unavailable, the tar and cpio front ends to libarchive (a.k.a. bsdtar and bsdcpio) can and will do so when reading through a pipe, meaning that the following is possible:

wget -qO- http://example.org/file.zip | bsdtar -xvf-

If you have the JDK installed, you can use jar:

wget -qO- http://example.org/file.zip | jar xvf /dev/stdin

I don't think you even want to bother piping wget's output into unzip.

From the wikipedia "ZIP (file format)" article:

A ZIP file is identified by the presence of a central directory located at the end of the file.

wget has to completely finish the download before unzip can do any work, so they run sequentially, not interwoven as one might think.

The proper syntax would be:

$ unzip <(curl -sL https://www.winpcap.org/archive/1.0-docs.zip)

but it won't work, because of the error (Info-ZIP on Debian):

lseek(3, 0, SEEK_SET)                   = -1 ESPIPE (Illegal seek)



Archive:  /dev/fd/63

  End-of-central-directory signature not found.  Either this file is not

  a zipfile, or it constitutes one disk of a multi-part archive.  In the

  latter case the central directory and zipfile comment will be found on

  the last disk(s) of this archive.

unzip:  cannot find zipfile directory in one of /dev/fd/63 or

        /dev/fd/63.zip, and cannot find /dev/fd/63.ZIP, period.

or on BSD/OS X:

Trying to read large file (> 2 GiB) without large file support

This is, because the standard zip tools are mainly using lseek function in order to set the file offset at the end to read its end of central directory record. It is located at the end of the archive structure and it is required to read the list of the files (see: Zip file format structure). Therefore the file cannot be FIFO, pipe, terminal device or any other dynamic, because the input object cannot be positioned by the lseek function.

So you have the following workarounds:

• use different kind of compression (e.g. tar.gz),


• you have to use two separate commands,


• use alternative tools (as suggested in other answers),


• create an alias or function to use multiple commands.

Repost of my answer:

BusyBox's unzip can take stdin and extract all the files.

wget -qO- http://downloads.wordpress.org/plugin/akismet.2.5.3.zip | busybox unzip -

The dash after unzip is to use stdin as input.

You can even,

cat file.zip | busybox unzip -

But that's just redundant of unzip file.zip.

If your distro uses BusyBox by default (e.g. Alpine), just run unzip -.

This works for me quite well:

tar xvf <(curl -sL http://www.vim.org/scripts/download_script.php?src_id=11834)



jar xvf <(curl -sL http://www.vim.org/scripts/download_script.php?src_id=11834)



wget -qO- http://www.vim.org/scripts/download_script.php?src_id=11834 | tar xvf -



wget -qO- http://www.vim.org/scripts/download_script.php?src_id=11834 | jar xvf -