On Nov 14, 11:25 am, Federico Capoano <nemesis.des...@libero.it> wrote: > No one is attacking your server, that's just the django server telling > you what's going on in your app (when you perform any action the > server logs it).
Right, but he said he's seeing requests that *can't* be explained by his own requests. I see this too when running runserver on the static IP of my dev box rather than on localhost. In my case, it's almost always requests from the university network security probes. It's actually satisfying to sit there watching requests for all kinds of known XSS attempts, security issues specific to common CMSs, etc., and see them all fail against Django. If you don't have security scanning happening on your network, it could be requests from crackers running port scanners or similar. Again, the solution is run runserver on 127.0.0.1, not on a public IP. ./s -- 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.
