I guess it depends with which mime-type the dmg file is sent.
> dev-apps-firefox mailing list
Is there any way for me to check this?
Also ... If I check "always do this for this type of file" shouldn't it
.. well ... do as it says?
Should I file a bug?
Well, you need to know with which mime-types the files are sent, to be
able to see what is going on.
What's the best way to find this out?
Is there an extension perhaps?
Or you might be able to see the http header with pasting the url here:
This might be tricky, though, because the server might react
differently in this case (but I don't think that happens often).
> _Michael Gorbach_ spoke thusly on 25/09/2006 10:14 AM:
>> On 2006-09-25 06:13:11 -0400, Martijn <martijn...@gmail.com> said:
>>> Well, you need to know with which mime-types the files are sent, to be
>>> able to see what is going on.
>> What's the best way to find this out?
>> Is there an extension perhaps?
As an example, downloading the following file pops up a dialog box
asking what to do with the thing (by the way, it also does not
correctly show the default app).
Downloading DMG files from macupdate gives no issues.
Is it because the content-type seems to be set to text-plain accord to
the web sniffer?
I get application/octet-stream as mime-type for that file.
What do you get when downloading a dmg file from macupdate?
Is the mimetype set correctly as dmg image? If so, FF is determining
these settings purely based on mimetype and not based on extension. It
needs to use both the extension and the mime. Even if it is not
possible, the "do this automatically for files like this from now on"
settings is not being applied correctly for dmg files sent by the web
server uunder application/octect-stream.
Seems like a bug to me.