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 14095] - Change default Content-Type (DefaultType) in default config
Date Tue, 13 Jan 2004 22:05:50 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=14095>.
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=14095

Change default Content-Type (DefaultType) in default config





------- Additional Comments From wrowe@apache.org  2004-01-13 22:05 -------
  Quoting an earlier comment...

  "application/octet-stream will allow the user agent to save the file or prompt 
   the user to make a decision, while application/x-unknown-content-type will 
   allow the user agent to actually sniff at the data and try to figure out what 
   it is."

  is entirely wrong w.r.t. Microsoft IE.

  IE has the irritating distinction of treating BOTH text/plain and also
  application/octet-stream as content type '*', parsing the data for some 
  possible meaning.  This causes IE to succumb to all sorts of mallicious
  purposes and undesirable side-effects of file naming.  (e.g. refusing to
  simply display a nice text/plain result of a result uri named 'test.pl',
  but instead insisting it aught to be locally executed or saved.)

  I agree with the spirit of the proposal, that our default become
  application/octet-stream until such time as we provide *no* content-type 
  whatsoever if the user has left it unconfigured.

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


Mime
View raw message