Accept my accept-language
blog.choibean.com
Accept my accept-language
1–10 of 76 posts
Re: Accept my accept-language
#2> 1. the default quality value is being parsed wrong, and English is being assigned q=0 instead of q=1 or
> 2. en-US doesn't match en and is being bypassed
Or: 3. They are simply checking your IP address and not looking at your header at all.
Re: Accept my accept-language
#3You probably want something like "en-US,en;q=0.9,ko;q=0.8". (Note the addition of "en" between "en-US" and "ko".) Some quick testing with Firefox, which lets you directly alter the Accept-Language: header in requests in about:config, shows that fedoraproject.org has "en" versions of resources but not "en-US" versions. Since your Accept-Language: header only lists "en-US", "ko" ends up being selected.
EDIT: I just noticed your guesses at the bottom of the post. Your second guess is correct. See §14.4 of RFC 2616:
As an example, users might assume that on selecting "en-gb", they will be served any kind of English document if British English is not available. A user agent might suggest in such a case to add "en" to get the best matching behavior.
Re: Accept my accept-language
#4> 1. the default quality value is being parsed wrong, and English is being assigned q=0 instead of q=1 or > 2. en-US doesn't match en and is being bypassed Or: 3. They are simply checking your IP address and not looking at your header at all.
His location is listed as California, so that wouldn't make much sense.
The current top poster actually figured out the exact issue in this case.
Re: Accept my accept-language
#5> 1. the default quality value is being parsed wrong, and English is being assigned q=0 instead of q=1 or > 2. en-US doesn't match en and is being bypassed Or: 3. They are simply checking your IP address and not looking at your header at all.
This is what so many websites do now. It causes me constant aggravation. It's nothing to do with your browser settings. They infer your language from your IP address, and for most cases that IS the right thing to do. However for me it isn't.
I really really wish there was a way to configure your browser to force websites to accept your language settings.
The only other option is to enable cookies so that the website language choice is saved - which also invites countless tracking cookies which I do NOT want.
Your web site does NOT know better than me which language I want to read.
Re: Accept my accept-language
#6I'm working on locale stuff for a Rails app right now (just updated the i18n_data in fact).
The assumption will be that country is mostly orthognal to language b/c people are übermobile. Further, that the dialect of the language should not force assumptions of other preferences... only autodiscover initial settings as close to desired as possible. (Fuck, why isn't there a standard for this common, hard-to-manage shit the OS already knows.)
i18n is taking up tons of time to get (mostly) right, but I believe it's one of those things not to botch because it's such a huge signal to everything else about your app.
If I want to be the most obscure hipster paying in Lesotho Loti, read Catalonian, have a "," for thousands separator and use UTC tz, by Flying Spaghetti Monster that's what it's gonna allow.
Re: Accept my accept-language
#7Google is^H^Hwas* really bloody annoying when it comes to this. English (en-us and en) is the only language in my accept header. When I lived in Geneva though, Google always used to serve me pages in German (presumably Swiss-German). Gee, that's logical. (Geneva is a mainly French speaking city, though over 40% of the population is non-Swiss.)
Where I live now is another French speaking area. I just checked and it seems they are no longer serving French pages to me. But they were even just one year ago. (I don't use Google by default, so I don't know when they changed.)
Admittedly, that was an issue with geo-detecting rather than the website having bad language detection.
* They seemed to have stopped.
Air France is (though they have many faults) actually alright at detecting my language. And mostly gives me English pages...
Re: Accept my accept-language
#8Google is^H^Hwas* really bloody annoying when it comes to this. English (en-us and en) is the only language in my accept header. When I lived in Geneva though, Google always used to serve me pages in German (presumably Swiss-German). Gee, that's logical. (Geneva is a mainly French speaking city, though over 40% of the population is non-Swiss.) Where I live now is another French speaking area. I just checked and it se…
IIRC google also "detects" language based on DNS geolocation, i.e. doing a dig google.com may reveal different IP addresses in every country (depending on the language).
There are some IP addresses which, when viewed "raw" like http://aaa.bbb.ccc.ddd/ will return a localized Google.
Re: Accept my accept-language
#9I'm working on locale stuff for a Rails app right now (just updated the i18n_data in fact). The assumption will be that country is mostly orthognal to language b/c people are übermobile. Further, that the dialect of the language should not force assumptions of other preferences... only autodiscover initial settings as close to desired as possible. (Fuck, why isn't there a standard for this common, hard-to-manage shit…
You might enjoy https://github.com/jcasimir/locale_setter
Re: Accept my accept-language
#10Google is^H^Hwas* really bloody annoying when it comes to this. English (en-us and en) is the only language in my accept header. When I lived in Geneva though, Google always used to serve me pages in German (presumably Swiss-German). Gee, that's logical. (Geneva is a mainly French speaking city, though over 40% of the population is non-Swiss.) Where I live now is another French speaking area. I just checked and it se…
I always have to open google.com/ncr in a separate tab which sets a session cookie (I don't accept permanent cookies from google.)
I guess they've changed their logic for some places, just not where I am :(