W3C home > Mailing lists > Public > ietf-http-wg@w3.org > October to December 1996

Re: Accept-Charset support

From: Koen Holtman <koen@win.tue.nl>
Date: Sun, 8 Dec 1996 12:43:43 +0100 (MET)
Message-Id: <199612081143.MAA16591@wsooti08.win.tue.nl>
To: Larry Masinter <masinter@parc.xerox.com>
Cc: koen@win.tue.nl, kweide@tezcat.com, http-wg%cuckoo.hpl.hp.com@hplb.hpl.hp.com, www-international@w3.org
X-Mailing-List: <http-wg@cuckoo.hpl.hp.com> archive/latest/2045
Larry Masinter:
># Content-Type: text/html;charset=utf-8
># Content-Features: utf-8-cs="<hebrew>" utf-8-cs="<latin-x>"
>There's no real point to this, though. The text/html;charset=utf8
>is enough to tell you how to interpret the body, and the body itself
>will tell you which repertoire(s) are used.

Yes.  Consider the above a bad example.  I should have written:

 Accept-Charset: utf-8
 Accept-Features: utf-8-cs="<hebrew>", utf-8-cs="<latin-x>", *

because we are really talking about how the user agent can make its
capabilities known to the server. 

The content-features header is not really useful.  It is only there for
symmetry with Accept-Features.  Even if it is present in a response, it is
not supposed to list all features used by the content, but only the features
that were negotiated on.  You should be able to know which features to use
by looking at the content itself.


Sorry for the confusion,

Received on Sunday, 8 December 1996 03:51:48 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 2 February 2023 18:43:00 UTC