On Wednesday March 25 2009, David C. Rankin wrote:
...
Now the veil of fog is starting to lift. So it isn't totally firefox, it's apache managing the mime-types and Firefox is just responding to what it gets?
That is true. When the server does not specify a MIME type or when the stream comes from a local file (and hence has no HTTP header where the MIME type and other metadata would be held), it falls back on using the file name suffix to infer a MIME type for the file's contents.
I've chased down ~/.mozilla/firefox/(garbage)/mimeTypes.rdf and changing it is no help at all. It's like a rubber-band, change it and it snaps right back to its old behavior. I just deleted it and forced a rebuild. Oh well, I never knew viewing a text file could be so much work...
That's 'cause you're trampling on the programmers' domain when they went to the trouble of giving you ~/.mime.types as means of overriding the built-in (or system-supplied) file-name-suffix-to-MIME-type mappings
Thanks again Sylvester
-- David C. Rankin
Randall Schulz -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org