W3C home > Mailing lists > Public > ietf-http-wg@w3.org > January to March 1997

Re: Please clarify * is legal in HTTP1/1 Accept-Charset Header

From: Koen Holtman <koen@win.tue.nl>
Date: Tue, 14 Jan 1997 09:18:06 +0100 (MET)
Message-Id: <199701140818.JAA22685@wsooti08.win.tue.nl>
To: Chris Lilley <Chris.Lilley@sophia.inria.fr>
Cc: koen@win.tue.nl, Chris.Lilley@sophia.inria.fr, ftang@netscape.com, http-wg%cuckoo.hpl.hp.com@hplb.hpl.hp.com, Alan_Barrett/DUB/Lotus.LOTUSINT@crd.lotus.com, Ed_Batutis/CAM/Lotus@crd.lotus.comi18ngrp, bobj@netscape.com, mduerst@ifi.unizh.ch, www-international@www10.w3.org
X-Mailing-List: <http-wg@cuckoo.hpl.hp.com> archive/latest/2291
Chris Lilley:
>On Jan 10,  7:53pm, Koen Holtman wrote:
>> > It would correct a
>> > sitiation where browsers send a list of things they do accept, followed
>> > by *, and this is (currently) often taken to mean exactly the same as
>> > if they had only sent the *.
>> In my opinion, this sitiatiomn should be corrected by changing the browsers
>> to send good accept headers, not by changing the spec to mandate some kind
>> of workaround in the server.
>Oh, certainly. I was just suggesting better defined behaviour for servers
>talking with existing clients.

It seems we agree then.  I guess the heuristics to deal with existing
clients could go into an implementation guide of some sort.

>Chris Lilley, W3C                          [ http://www.w3.org/ ]

Received on Tuesday, 14 January 1997 00:32:42 UTC

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