firefox backwards compatability bug

[drhowarddrfine]

Here is the answer. What you linked to, above, is from 1992 and is out of date. The current HTTP1.1 published standard says this:

If and only if the media type is not given by a Content-Type field, the recipient MAY attempt to guess the media type via inspection of its content and/or the name extension(s) of the URI used to identify the resource. If the media type remains unknown, the recipient SHOULD treat it as type "applicatio n/octet-stream".

So, as usual, Firefox is performing correctly and to the standard and your shaming of it should actually be a shame on IE for not performing correctly, as usual.

[Plater]

"may" attempt does not mean it has to.

HTTP/1.1 standards also dictate to support HTTP/1.0. (I had linked to the http/1.0 standards...or at least I had ment to)

Regardless of following standards or not, it's still locking up when it clearly shouldn't be. Perhaps a bug in the acrobat plugin though.

[drhowarddrfine]

As the Firefox developers told me to ask you, what do you expect it to do with it then? The alternative is to do nothing. Firefox is performing correctly and to the letter of the standard. IE is not. In any case, you are supposed to provide content type.

Firefox is not locking up for me but I don't have Acrobat on this machine.

[drhowarddrfine]

More info. The link you showed in your first post is archived under "Old Documents" which have: "Archive document status are useful but dated documents with no guarantee that they are up to date. "

HTTP/1.1 standards also dictate to support HTTP/1.0.

It says the same in http1.0