Downloading files compressed in transport with download-url

[adswa]

Origin: DataLad core issue tracker, issue #7433

A user downloaded a file that was compressed in transport with datalad download-url. Internal checks in this command compare the size reported in the response header with the size of the downloaded file. As compressed files get automatically decompressed, the size reported in the header and the file size on disk after decompression mismatched.
This resulted in an error and abortion of the download.

datalad-next's download command has already learned to account for this difficulty, and can download files without a problem.
However, the user did not have datalad-next installed, and thought their datalad version was too old. In turn, they stuck to wget followed by a manual gunzip.
So although there is a solution to allow downloads, it isn't ideal. I believe this support issue requires datalad core to handle such cases, too, for example by ingesting next code.

I believe that what the issue showed apart from a legit bug in datalad is a factor of user confusion with regard to datalad-next.
We should resolve or improve this, either with documentation or internal project or dependency management.

TODO (not necessarily to be performed in this order)

• Inform OP/Add reference to this issue at origin
• Clarifying Qs asked or not needed
• Nature of the issue is understood
• Inform OP about resolution