bug 258246: RFC: Accept language header: 'en-gb' and matching

Max Kanat-Alexander mkanat at kerio.com
Mon Sep 13 22:59:53 UTC 2004

> Gervase Markham wrote:
> > David Miller wrote:
> > 
> >> But that's not what the RFC says, and it's not how Apache works for 
> >> the built-in content-negotiation it can do.
> > 
> > But isn't it common-sense?
> > 
> > Someone sends:
> > Accept-Language: de-de, fr
> > 
> > And we have a choice of de and en, with default as en. What would be the 
> > sensible thing to serve them?

	My best guess as to the reasoning behind the RFC has probably to do
with Asian languages, where the thing after the dash is incredibly
important. For example, as far as I'm aware, there are dialects of
Chinese that cannot be read or understood easily by other people who
also speak a language called "Chinese."

	I'm not sure if there are Western languages that have this issue.

	Still, I would think that it's better to serve the user something that
they can at least attempt to use, rather than give them nothing.

Maxwell Kanat-Alexander
2nd Level Tech Support Engineer, USA
Kerio Technologies, Inc.
2041 Mission College Blvd. Suite 100
Santa Clara, CA 95054
Phone: (408) 496-4500
Fax: (408) 496-6902
Web: http://www.kerio.com/support.html

More information about the developers mailing list