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

Re: Accept-Charset support

From: Larry Masinter <masinter@parc.xerox.com>
Date: Sat, 7 Dec 1996 16:30:43 PST
To: koen@win.tue.nl
Cc: kweide@tezcat.com, http-wg%cuckoo.hpl.hp.com@hplb.hpl.hp.com, www-international@w3.org
Message-Id: <96Dec7.163043pst."2694"@golden.parc.xerox.com>
X-Mailing-List: <http-wg@cuckoo.hpl.hp.com> archive/latest/2043
# 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.

# 9.3 Content-Features
#   The Content-Features response header can be used by a server to
#   indicate how the presence or absence of particular features in the
#   user agent affects the overall quality of the response.
#       Content-Features = "Content-Features" ":" feature-list

how does the 'content-features' actually indicate this? This is
confusing to me. Is content-features actually useful at all?
In general, you don't want to list ALL the features that a given piece
of content might exhibit, you only want those that are used to
distinguish one content from another for the purpose of transparent
feature negotiation.

Received on Saturday, 7 December 1996 16:37:46 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:16:21 UTC