Richard Clark wrote in
:

....
Jeff obviously knows exactly how Microsoft servers work.

So, the server is asking (which is what request means) the client for
the MIME type?

I doubt it.

What a yuk. And using M$ as the gold standard for
providing non-HTTP compliant servers? Yuk² Quite literally, M$ does
not know how HTTP servers are supposed to work.

"MIME is currently defined in RFCs 2045, 2046, 2047, 2048, and
2049 and registered values for MIME types are available in IANA |
MIME Media Types. The HTTP specification defines a superset of
MIME which is used to describe the media types used on the web."

While some are stressing about getting IANA registration of the ez
extension, it already is, and to another application, and its type is
application/andrew-inset.

So, many web servers (using the IANA MIME media type list) will serve the
file up with a HTTP Content-Type of application/andrew-inset . That won't
affect most users, because their browser will not have any defined action
for that application type.

On a good web server, one could override that MIME association for the
file, files, directory or tree... but it shouldn't be necessary.

Owen