Well, OK. I mean, technically, that's correct. Uhm... but, right, we know that
in the real world things aren't always exactly to spec, like
"http://bla.com/bla"; gets mapped to "http://bla.com/bla/"; (server fails the
first time, then inserts the trailing slash) -- so, could there be some
(hidden? in the user.js file or whatetever) pref to have Camino basically treat
all text as HTML? Or at least, before concluding that it's *not* to be
rendered, to do one more check and see if the content begins with "<html>"?
uhm, if you check this list's archives, you'll find endless threads on the same subject, mainly about disk images (DMG) shown as text.
The 2 main parties are who thinks it's all about the sysadmins, and who thinks CAmino, like other browsers, should sniff content and override MIME types sent by the server.
I am a bit undecided, regarding binaries like disk images, but I tend to support the first option (wake up, lazy admin!) if common text files aren't served like they should.
In the case of server side scripts, like ASP, it could also be the scripter who chose to send text/plain, via custom header.
Ciao. Marcello.
_______________________________________________ Camino mailing list [EMAIL PROTECTED] http://mozdev.org/mailman/listinfo/camino
