[hawken]

I've been having this really strange issue with Safari lately. Actually, it's affecting any browser that uses Apple's rendering engine, like WebKit or OmniWeb 5.5. In many cases, when I download a .dmg from a site, Safari is adding a .bz2 extension to the end of the file. If you then try to decompress the file, you end up with a corrupted .dmg.

Initially, I thought it was a problem coming from particular sites. I started noticing it more regularly, however, so I tested with Firefox, and a windows machine and discovered they downloaded a perfectly usable .dmg that was now .bz2 compressed. I even tried wget, and it worked fine, too.

Since it seems to be affecting Safari, I tried to thing about what I may have installed to cause this. I don't use any Safari add-ons, and I had tried out a couple of shareware compression apps (Unachriver and Compress), which could have caused the problem. I've zapped them with appzapper, so they should be out of the picture.

I did discover this morning that if I rename the .dmg.bz2 to simple .dmg, they are mountable like normal, so it doesn't look like the files are even really beign compressed - it's just that extension getting added. I just can;t figure out what in the world is adding the extension.

Any ideas?

Thanks!

[TETENAL]

Safari adds an extension according to the mime type the server sends the file with. The servers might send the disk images with the wrong mime type.

[Chuckit]

Just to clarify, are the files you're downloading bzip2-compressed or not? And would it be possible to link a sample file that displays the problem so we could see?

[Mithras]

What TETENAL said. Safari adjusts the extension according to the mime type, which often works well but sometimes goes awry, i.e. when the web server delivers the wrong mime type. Since .dmg is pretty much a Mac-only extension, many web servers do not have it properly configured.