#12197: parse_accept_lang_header parse HTTP_ACCEPT_LANGUAGE with wrong Quality
factors
-------------------------------------------+--------------------------------
Reporter: [email protected] | Owner: nobody
Status: closed | Milestone: 1.2
Component: Internationalization | Version: 1.1
Resolution: invalid | Keywords:
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
-------------------------------------------+--------------------------------
Changes (by ramiro):
* status: new => closed
* has_patch: 1 => 0
* resolution: => invalid
Comment:
There is a test case in the Django test suite that test exactly for a
header value almost identical to the one you posted that demonstrates the
algorihtm is working as expected:
http://code.djangoproject.com/browser/django/trunk/tests/regressiontests/i18n/tests.py?rev=12373#L394
The fact that the list after splitting the header value by the RE is
represented by three consecutive items for each lang specification element
is by design and the value of the first one (`first` variable) is used to
detect incorrectly formatted values if not empty, and then discarded.
So, I don't know your report is because of an issue you are seeing in real
world usage or the result of a theoretical analisys. If it's the former
please post more details, in the meantime I'm marking this ticket as
invalid.
--
Ticket URL: <http://code.djangoproject.com/ticket/12197#comment:3>
Django <http://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
