Hi,
I had broken link emails enabled for a while. Over time, my nginx.conf
config grew into this:
location /_vti_inf.html { return 404; }
location /crossdomain.xml { return 404; }
location ~/cache/eb91756ae6745d22433f80be4ec59445$ { return 404; } #
some sort of plugin?
location
Hi,
thanks for your reply.
Blocking all requests in Apache seems to be the best way. Can you give an
example how to do that?
As / is mapped to the wsgi app (
https://docs.djangoproject.com/en/1.7/howto/deployment/wsgi/modwsgi/ )
and a new files section does not the trick:
#PHP p
you can tell apache to get any request ending with .php and return 404 from
apache without passing the request to django
you could return something else like 403 and ban the ip for some time
On Tue, Jan 20, 2015 at 1:55 PM, hinnack wrote:
> Hi,
>
> I get a lot of intrusion checks on my website -
Hi,
I get a lot of intrusion checks on my website - especially for PHP
(wordpress, joomla, …).
Today they all raise a 404 errors in python-django - so if you have emails
enabled for 404 errors…
What is the best way to block those requests in a standard apache
deployment?
( https://docs.djangop
4 matches
Mail list logo