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 23421] - Remove AddDefaultCharset from httpd.conf as shipped
Date Sun, 01 Aug 2004 10:42:48 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=23421>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=23421

Remove AddDefaultCharset from httpd.conf as shipped





------- Additional Comments From nick@webthing.com  2004-08-01 10:42 -------
I agree that shipping with an AddDefaultCharset preset is unsatisfactory,
and screws up users of servers with unresponsive admins.

Can we simply remove it from the default config to deal with the case of authors
having more clue than their sysops?  I'd be happy with that, but I'm going to
ask for review in other fora where folks have relevant expertise.

Actually the solution is already available to users.  There's a bunch of
AddCharset directives in the default httpd.conf that serve precisely this
purpose:
AddCharset ISO-8859-1  .iso8859-1  .latin1
AddCharset ISO-8859-2  .iso8859-2  .latin2 .cen
AddCharset ISO-8859-3  .iso8859-3  .latin3
etc.

So a fix would be to correct errors and omissions in that list, and leave it
to authors to control their charset using a suffix on the document name.
Of course that's ugly, but at least it works.

Also worth noting: mod_proxy_html 2.x will parse META elements in
HTML and XHTML documents and convert them to real HTTP headers.
See http://apache.webthing.com/mod_proxy_html/

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


Mime
View raw message