You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I get the value for en-UK using getBest and based on my (admittedly new) reading of the RFC suggests that I should get the 'en-US' value since it is listed first and they have the same quality factor. (Common sense suggests that is the better value.)
Switching the accept string to be en-US, *;q=0 resolves the matter but seems either incorrect or at least unnecessary.
Am I doing something wrong or is this a bug? It looked similar to some of the other open issues, but not quite the same. It also wasn't a problem in the 1.x release series.
The text was updated successfully, but these errors were encountered:
Given a list of languages like:
['en-US' => '...', 'en-UK' => '....']
And a language string of:
en-US, *
I get the value for
en-UK
usinggetBest
and based on my (admittedly new) reading of the RFC suggests that I should get the 'en-US' value since it is listed first and they have the same quality factor. (Common sense suggests that is the better value.)Switching the accept string to be
en-US, *;q=0
resolves the matter but seems either incorrect or at least unnecessary.Am I doing something wrong or is this a bug? It looked similar to some of the other open issues, but not quite the same. It also wasn't a problem in the 1.x release series.
The text was updated successfully, but these errors were encountered: