httpd-bugs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 13986] - remove default MIME-type
Date Wed, 05 Feb 2003 12:44:59 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13986>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13986

remove default MIME-type





------- Additional Comments From info@orangexl.com  2003-02-05 12:44 -------
   Maybe. But that's the only way every software works. So that difference is
   not very interesting for now.

It is, because in this case the HTTP-RFC states the client should decde what is 
the appropriate MIMI-type


   ??

Sorry, I meant to that sending the Content-Type octet-stream (as suggested 
earlierer) in cases Apache doesn't know the MIME-type goes against the HTTP-RFC 
(which states the client should make this decision)

 
   Again: you can teach apache these types. That shall be wrong? Can't 
   believe that.

Yes you can, but if that is what you want, Apache should include these MIME-
types by default.


   If the author intends a content type, he can advise the httpd in various
   ways to send it. All of these ways are quite simple.

But the DefaultType has nothing to do with intending a content-type. Or, I 
don't think many webmasters use it this way...


  *sigh* we spin round again and again.

Perhaps this is a discussion for the Apache developers maillinglist.


  Neither the server nor the client knows what is sent. They both have to be
  configured to recognize something. Let the people configure their software
  properly and everything is fine. Don't blame apache for dumb admins. Blame
  the ISPs!

Indeed, people's software should be properly configured. But if this is the 
case, Apache should not send a Content-Type header for unknown content! 
Otherwise, people's software cannot recognize what Apache is sending! 
(remember, if Apache sends a content-type, the client MUST not question it, 
according to the HTTP-RFC)


  I don't believe that. But however, this is not a problem. I'm also concerned
  about compat. The Apache doesn't exist only for Mozilla. What about the
  thousands of browsers out there? How do they work without getting a content   
  type?

That is a concern, but is it Apache's problem? Browsers should work according 
to the HTTP-RFC (that's why they are for). If they don't, should Apache also 
disregard the HTTP-RFC?


  I don't know, are there any infos available?

To my knowledge, IE should work fine. Many other browsers look at file's 
extesions to guess the MIME-type.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org


Mime
View raw message