On Wed, Jul 14, 2010 at 6:47 PM, George Sakkis <george.sak...@gmail.com> wrote: > On Jul 12, 3:59 pm, Andi <apoi...@gmail.com> wrote: > >> On Jul 12, 3:40 pm, Nick Raptis <airsc...@otenet.gr> wrote: >> >> > Yea, for some reason, my thoughts went to Weave too. Maybe it has >> > something to do with it, maybe it doesn't. Haven't got any more trouble >> > since I fixed it though. >> > Glad I could help :) >> >> I'm using Weave too, don't think that's a coincidence. > > Another Weave user here, and I confirm both the problem and the > solution. > > Thanks a lot for solving this, it was driving me crazy!
I'm glad we've worked out that Weave is the culprit, but nobody has answered the question of whether this is an indicator of a problem with Django itself. What is weave passing as a header (and under what conditions) that is causing a problem? Is there a need to improve Django's error handling to protect against this case? 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.
