On Fri, Sep 3, 2010 at 2:04 PM, dave b <db.pub.m...@gmail.com> wrote: > Ok no movement :)
Nor is there likely to be. Insofar as you've identified a problem at all, it's a problem in a piece of software that isn't Django, and you've ignored multiple people who've pointed that fact out to you (along with the fact that Apache behaves exactly as documented and that we expect people to know how to configure their web server to suit their needs, use cases and threat models). So what, precisely, are you hoping to gain from continuing this thread? -- "Bureaucrat Conrad, you are technically correct -- the best kind of correct." -- 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.
