From owner-freebsd-www  Tue Feb  3 10:47:10 1998
Return-Path: <owner-freebsd-www>
Received: (from daemon@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id KAA11330
          for www-outgoing; Tue, 3 Feb 1998 10:47:10 -0800 (PST)
          (envelope-from owner-freebsd-www)
Received: from fallout.campusview.indiana.edu (fallout.campusview.indiana.edu [149.159.1.1])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA11323
          for <www@freebsd.org>; Tue, 3 Feb 1998 10:47:08 -0800 (PST)
          (envelope-from jfieber@indiana.edu)
Received: from localhost (jfieber@localhost)
	by fallout.campusview.indiana.edu (8.8.7/8.8.7) with SMTP id NAA18511;
	Tue, 3 Feb 1998 13:42:42 -0500 (EST)
Date: Tue, 3 Feb 1998 13:42:42 -0500 (EST)
From: John Fieber <jfieber@indiana.edu>
Reply-To: John Fieber <jfieber@indiana.edu>
To: www@jp.freebsd.org, www@FreeBSD.ORG
Subject: content-type headers
Message-ID: <Pine.BSF.3.96.980203133643.16473K-100000@fallout.campusview.indiana.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-www@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

It seems to me that it would be correct to add:

  <Location /ja_JP.EUC/>
  AddType "text/html; charset=EUC-JP" .html
  </Location>

to the server config on www.freebsd.org so the HTTP headers
correctly reflect the content type.  According to the HTTP/HTML
standards, the content-type in the HTTP header takes precedence
over the content-type in an HTML <META> tag, so we may as well
now make the HTTP headers correct. 

Am I wrong?  Is there a better way?

-john