Re: p2: Accept-Language missing, empty or no match

Mark Nottingham <mnot@mnot.net> Tue, 07 May 2013 05:16 UTC

Resent-Date: Tue, 07 May 2013 05:15:11 +0000
Resent-Message-Id: <E1UZaF5-0003Z5-69@frink.w3.org>
Content-Type: text/plain; charset="iso-8859-1"
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <n2o0o8tt6miq9ljs4pr47l6p2s8hgi6hb4@hive.bjoern.hoehrmann.de>
Date: Tue, 07 May 2013 15:14:34 +1000
Cc: "ietf-http-wg@w3.org Group" <ietf-http-wg@w3.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <60F8768B-E166-4002-B96E-55737C4CBBA1@mnot.net>
References: <8741FE69-C013-4853-A9A3-6321A18E56EA@mnot.net> <2896D8B9-399D-4F68-9BC1-9EFDB893C2BE@mnot.net> <sn5vn8pe3hins3oeghba9qrkcooustfmg8@hive.bjoern.hoehrmann.de> <21D17E62-229B-41E2-A7E5-9623A52DE3C2@mnot.net> <n2o0o8tt6miq9ljs4pr47l6p2s8hgi6hb4@hive.bjoern.hoehrmann.de>
To: Bjoern Hoehrmann <derhoermi@gmx.net>
Received-SPF: pass client-ip=216.86.168.182; envelope-from=mnot@mnot.net; helo=mxout-07.mxes.net
Subject: Re: p2: Accept-Language missing, empty or no match
Archived-At: <http://www.w3.org/mid/60F8768B-E166-4002-B96E-55737C4CBBA1@mnot.net>
Resent-From: ietf-http-wg@w3.org
Resent-Sender: ietf-http-wg-request@w3.org
Precedence: list

Proposal updated in ticked and marked for -23.

<http://trac.tools.ietf.org/wg/httpbis/trac/ticket/448#comment:4>

Thanks,


On 01/05/2013, at 10:35 AM, Bjoern Hoehrmann <derhoermi@gmx.net> wrote:

> * Mark Nottingham wrote:
>> Good point. 
>> 
>> how about:
>> 
>> """
>> A request without any Accept-Language header field implies that the user 
>> agent will accept any language in response. If an Accept-Language header 
>> field is present in a request and none of the available representations 
>> for the response have a language tag that is listed as acceptable, the 
>> origin server MAY either disregard the Accept header field by treating 
>> the response as if it is not subject to content negotiation, or honor 
>> the Accept header field by sending a 406 (Not Acceptable) response. 
>> However, the latter is not encouraged, as doing so can prevent users 
>> from accessing content that they might be able to use (with translation 
>> software, for example).
>> """
> 
> Two cases of s/Accept/Accept-Language/. "MAY either ... or ..." is bad
> usage of RFC 2119 terms. And I don't like the implication that sending
> anything other than 406 is "not honoring" the Accept-Language header.
> But this is close enough to say "works for me".
> 
> Thanks,
> -- 
> Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de
> Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de
> 25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/ 
> 

--
Mark Nottingham   http://www.mnot.net/

p2: Accept-Language missing, empty or no match Mark Nottingham
Re: p2: Accept-Language missing, empty or no match Mark Nottingham
Re: p2: Accept-Language missing, empty or no match Mark Nottingham
Re: p2: Accept-Language missing, empty or no match James M Snell
Re: p2: Accept-Language missing, empty or no match Bjoern Hoehrmann
Re: p2: Accept-Language missing, empty or no match Mark Nottingham
Re: p2: Accept-Language missing, empty or no match Bjoern Hoehrmann
Re: p2: Accept-Language missing, empty or no match Willy Tarreau
Re: p2: Accept-Language missing, empty or no match Mark Nottingham
#448, was: p2: Accept-Language missing, empty or … Julian Reschke
Re: #448, was: p2: Accept-Language missing, empty… Mark Nottingham
Re: #448, was: p2: Accept-Language missing, empty… Julian Reschke
Re: #448, was: p2: Accept-Language missing, empty… Mark Nottingham
Re: #448, was: p2: Accept-Language missing, empty… Julian Reschke