The ".htm" is only in the extension of the file being read. The filename being sent is set to ".ppt".
Adding in the '.' in the content-type header had no effect.
Removing the "<html>" tags from the html file had no effect.
The IE links are excellent, and contradictory. I'd like to cling to:
Mimesniffing doesn't mean that there is no way for a server to control how a file is handled. <Content-disposition: attachment; filename="filename.ext"> header enables a server to do precisely that. With this however, IE makes sure that the user gets prompted with the file type information (based on the extension specified by the server here) before the file is opened/saved.
but the current experience is proving that hope false.
Forget that fear of gravity,
Get a little savagery in your life.
In reply to Re: Sneding MIME type headers not forcing desired behaviour.
by punch_card_don
in thread Sending MIME type headers not forcing desired behaviour.
by punch_card_don
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |