On Thu, Jul 15, 2010 at 7:33 PM, Nick Raptis <airsc...@otenet.gr> wrote: > On 07/15/2010 02:20 PM, Russell Keith-Magee wrote: >> >> You, mean, like... oh, I don't know... one of the core developers of >> Django? Like the one that's been asking for details on how to >> reproduce the problem? :-) >> >> Yours, >> Russ Magee %-) >> >> > > Ahhhhhaha! Exactly! Nice to make your acquittance Russ. > Knowing who is who is a bit of magic art on lists, unless of course you > google every email :) > > To my mind, the devs and the site maintainers don't have to be the same > people, but I threw it on the list so someone (turns out to be you) could > get the word through. > Mischief managed :)
Ok - problem found. In django/utils/translation/trans_real.py, the parse_accept_lang_header() function uses a regular expression to check for valid languages. That regular expression (accept_language_re) looks for language components up to 16 characters in length. It looks like some extra error handling may be required. I've opened ticket #13944 to make sure the issue isn't forgotten. Thanks to all that helped to identify the issue. Yours, Russ Magee %-) -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
