On Thu, Jul 15, 2010 at 11:02 AM, George Sakkis <george.sak...@gmail.com> wrote: > On Jul 15, 4:55 am, Danny Adair <danny.ad...@unfold.co.nz> wrote: > >> Hi, >> >> I had the exact same problem, and I had _not_ installed Weave. >> The offending config entry in my case was: >> "chrome://global/locale/intl.properties" >> and it was at the bottom of the accepted languages list. This is on >> Firefox 3.6.6 >> >> I can reproduce the problem anytime by visiting about:config and >> changing "intl.accept_languages" to >> en-nz,en,de,chrome://global/locale/intl.properties >> >> *.djangoproject.com will stop responding, (all?) other websites seem fine. > > I didn't write down the offending entry in my case but I think it was > the same or similar to yours. In any case, I can confirm that by > setting it the problem is reproduced. > > Trying to reverse engineer the pattern of the offending values, I > believe that the issue is the string length: any value up to 16 bytes > works fine, 17 or more hangs. > > George >
Hmm - mine is way longer than 17 characters, and I do not have any issues. intl.accept_languages="en-US,en,fr-FR,fr,ja-JP,ja,en-GB,nl-NL,nl,en-gb" works just fine for me. Maybe firefox version is pertinent. This is firefox-3.6.4,1 from ports on FreeBSD 7/i386. Hmm, adding 'chrome://global/locale/intl.properties' does affect it... Using wireshark to capture the traffic it seems no response is sent for the offending request. I've created a minimum test case that can be used to trigger the situation, using nc (nc will just hang waiting for a response): > $ nc www.djangoproject.com 80 < django_http_fail.req django_http_fail.req: GET http://www.djangoproject.com/ HTTP/1.1 Host: www.djangoproject.com Accept-Language: en;q=0.9,chrome://global/locale/intl.properties;q=0.1 The good news (on some part) is that this doesn't seem to affect all django sites. None of my sites become inaccessible after making these changes. I guess djangoproject.com has some middleware that gets stymmied by this invalid entry. Cheers Tom -- 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.
