I have some .mht files that open fine locally in Chrome and am trying to serve them through a web server. I've tried a number of combinations of with
Content-Type and
Content-Disposition headers, but can't get things to render properly. The page is either rendered in text (showing the underlying MIME message), or it forces a download (i.e. the save file dialog pops up). If I examine the
Accept request header from Chrome, I don't see
multipart/related or
message/rfc822, so maybe I shouldn't be surprised that it doesn't work.
Does anybody know if it's possible to have an .mht file served to Chrome without forcing a download of the file?
Regards,
John