Welcome to WebmasterWorld Guest from

Forum Moderators: phranque

Message Too Old, No Replies

FireFox downloading page instead of rendering it

10:42 pm on Jun 30, 2008 (gmt 0)

New User

5+ Year Member

joined:June 30, 2008
posts: 10
votes: 0

I think RFC 2616 should be revised.

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

I appreciate any comments on this.

11:04 pm on June 30, 2008 (gmt 0)

Senior Member

WebmasterWorld Senior Member jdmorgan is a WebmasterWorld Top Contributor of All Time 10+ Year Member

joined:Mar 31, 2002
votes: 0

Now try forcing IE (which is more "forgiving") to heed the HTTP Content-type header when it is set correctly by the server...

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. :)


9:23 pm on July 7, 2008 (gmt 0)


WebmasterWorld Administrator coopster is a WebmasterWorld Top Contributor of All Time 10+ Year Member

joined:July 31, 2003
votes: 1

Welcome to WebmasterWorld, Lassar.

jdMorgan has summed it nicely IMHO.