It is true that the server sends back "Content-Type: application/octet-stream"
for this url.
nevertheless, it seems like whatever IE does in this respect should be mimic'd.
i'm not sure how IE decides that an .exe is to be downloaded, while a .cpp
is to be displayed; perhaps it actually looks at the content itself to guess.
or maybe it has a builtin list of "text-like" suffixes.
on a similar note, i know of a server that had been inadvertantly set to a default type of text/plain instead of text/html (since corrected)... k-meleon displayed the html source for the page, taking it at it's word, but IE somehow 'knew' to display an html page... i don't really know about the advisability of trying to mimic the non-standard behavior of IE, but i guess it's apt to be an issue...
maybe the user could choose between a 'smart' mode and a 'literalist' mode...