Forum Moderators: phranque
I think RFC 2616 should make an exception for a special case where content type says it is "application/".
An example of this is "application/x-httpd-php".
Which would be treated as a download"
But if the extension says .htm, .html, .asp, .php , etc ; then I think you should check the content to see if it is a web page.
If it is; then render it.
Especially since you have incompetent web developers/ web masters out on the web.
The Browser should be more forgiving in this case.
But for FireFox the only way to get this changed is to get RFC 2616
revised.
I appreciate any comments on this.
Firefox was written to comply with the specification and use the Content-Type header, not ignore it and try to 'interpret' the content. The Web is replete with posts about how to overcome IE's non-compliance on this issue.
What do you propose to do if the file has no extension -- a growing trend among savvy sites?
I'll take standards, thanks. :)
Jim