On Wed, Apr 16, 2014 at 12:38 PM, Tom Evans <tevans...@googlemail.com> wrote:
> On Wed, Apr 16, 2014 at 1:24 PM, Mauricio Tavares
> <raubvo...@gmail.com> > I guess I am more paranoid than many. :)
>
> The internet is noisy and full of terrors.
>
> If you put a server, particularly http server, on the internet and
> make it available, people will make all kinds of requests to it - not
> necessarily requests that you were anticipating.
>
> If you look carefully at the requests in that access log, all the
> requests failed. Most failed with an internal server error, others
> with a timed out request.
>
> OP: Are you actually running a bittorrent tracker on the server (or
> have you ever)? It looks like the requests for the tracker are the
> internal server error requests.
>
> Also, do those domain names resolve to your IP address? Has the owner
> of those urls mistakenly added your IP as an alias? Is this a new IP
> address that used to belong to them and they haven't updated their
> DNS?
>
> If you can't get the requests to stop, nor change to a different IP,
> the best you can do is to route them to a default vhost that simply
> rejects all requests. This ensures that only requests for your
> hostname are handled for your actual site; all these bad requests
> would be handled by the default vhost.
>
Ok, so it is not as bad as I thought. In that case, I would
suggest the OP to consider using fail2ban
> Cheers
>
> Tom
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
> For additional commands, e-mail: users-h...@httpd.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org
