“latest.tar.gz” is tar’d but not gzip’d

Does Otto’s answer help?
https://www.ads-software.com/support/topic/135594?replies=2

I just downloaded the file, it is indeed tar’d and gzip’d. If you got it ungzip’d, then your browser or web downloader expanded it for you (most browsers understand gzip).

The correct filesize (and the one I got) is 870,766 bytes. If yours is bigger, your browser expanded it.

This is because wget recognized that it was gzipped and the server was sending application/octet-stream (instead of application/gzip).

You’re right; I tried it on another linux box and received the same thing with wget and links, but in firefox, it downloaded a gzip’d version. Weird. I’ve downloaded via wget before (<2.3 versions) and I always used the command: tar zxvf latest.tar.gz to decompress/untar. There seems to have been a server change on the www.ads-software.com end.

The problem has been fixed by Barry (copy-pasted from wp-hackers mailing list):

So, here’s the technical explanation:

It had nothing to do with the User-Agent but with the HTTP request
headers that were sent. By default CLI utilities such as wget and curl
dont send any Accept-Encoding headers. Server side we were sending a
‘Content-Encoding: gzip’ header for the tar.gz file. Since there was no
‘Accept-Encoding: gzip’ header sent by the client, an uncompressed
version was delivered to the client. It’s pretty inconvenient (as you
noticed) to have a tar.gz file that is uncompressed.

I have removed the Content-Encoding header and replaced it with the
correct Content-Type headers to identify the different download types.