W3C home > Mailing lists > Public > www-international@w3.org > October to December 1996

Re: Accept-Charset support

From: Martin J. Duerst <mduerst@ifi.unizh.ch>
Date: Thu, 5 Dec 1996 12:42:01 +0100 (MET)
To: Larry Masinter <masinter@parc.xerox.com>
cc: Alan_Barrett/DUB/Lotus.LOTUSINT@crd.lotus.com, www-international@w3.org, bobj@netscape.com, wjs@netscape.com, Chris.Lilley@sophia.inria.fr, erik@netscape.com, Ed_Batutis/CAM/Lotus@crd.lotus.com
Message-ID: <Pine.SUN.3.95.961205123636.279D-100000@enoshima>
On Wed, 4 Dec 1996, Larry Masinter wrote:

> #However, I am worried that the Accept-Charset may not take a "*" wildcard 
> #parameter. Does anyone know?
> 
> http://ds.internic.net/internet-drafts/draft-ietf-http-v11-spec-07.txt
> 
> > If no Accept-Charset header is present, the default is that any
> > character set is acceptable. If an Accept-Charset header is present, and
> > if the server cannot send a response which is acceptable according to
> > the Accept-Charset header, then the server SHOULD send an error response
> > with the 406 (not acceptable) status code, though the sending of an
> > unacceptable response is also allowed.

Does the 406 response include some information on what "charset"s would
indeed be acceptable? If not, some of the considerations that I made
in other mails to this list seem to suggest that "sending an unacceptable
response" may be rather better than not sending anything.

Regards,	Martin.
Received on Thursday, 5 December 1996 06:43:18 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 2 June 2009 19:16:46 GMT