Mailing-List: contact users-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@httpd.apache.org
Received-SPF: neutral (asf.osuosl.org: local policy)
From: Nick Kew <nick@webthing.com>
Organization: WebThing Ltd
To: users@httpd.apache.org
Date: Wed, 1 Feb 2006 09:33:36 +0000
User-Agent: KMail/1.8.3
References: <20060201054118.95771.qmail@web53809.mail.yahoo.com>
In-Reply-To: <20060201054118.95771.qmail@web53809.mail.yahoo.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200602010934.45423.nick@webthing.com>
Subject: Re: [users@httpd] AddDefaultCharset and Multiple Encodings

On Wednesday 01 February 2006 05:41, Skating Jim wrote:

> The basis for my comment is that the Apache
> documentation for AddDefaultCharset says:
>
> "This should override any charset specified in the
> body of the response via a META  element, though the
> exact behavior is often dependent on the user's client
> configuration."

That's just FYI.  What matters is not the Apache documentation,
but the public internetworking specs: RFC2616 (HTTP), and the
MIME one whose number I don't recollect without looking it up.

So what the apache documentation is really telling you is how
an Internet-compliant browser works.  It qualifies that by noting
that some browsers may be broken.

-- 
Nick Kew

---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
   "   from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org