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

[Mark Nottingham <[e-mail]>]

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).
"""

On 30/04/2013, at 8:07 PM, Bjoern Hoehrmann <[e-mail]> wrote:

> * Mark Nottingham wrote:
>> Anyone disagree with adding similar text to Accept-Language? If not, I'll mark for incorporation.
> 
> I certainly disagree with adding text suggesting it's as good an idea to
> respond with 406 due to Accept-Language as it is to respond with 406 due
> to Accept, Accept-Charset, or Accept-Encoding, the latter all being ca-
> pabilities of the user agent, while Accept-Language refers to the user's
> education. Back in the day I had to add `*` to my Accept-Language header
> to avoid this failure case, which was indeed present on several sites. I
> could probably live with noting 406 is okay "somehow", but the text must
> be very different from the text for the other headers.
> -- 
> Björn Höhrmann · mailto:[e-mail] · http://bjoern.hoehrmann.de
> Am Badedeich 7 · Telefon: [phone] · http://www.bjoernsworld.de
> 25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/ 

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