Slicehost Forum - Blocking an IP Address with Passenger Thu, 09 Sep 2010 18:42:27 +0000 http://forum.slicehost.com/ Lussumo Vanilla 1.1.8 Blocking an IP Address with Passenger http://forum.slicehost.com/comments.php?DiscussionID=3993&Focus=21616#Comment_21616 http://forum.slicehost.com/comments.php?DiscussionID=3993&Focus=21616#Comment_21616 Mon, 10 Aug 2009 16:47:28 +0000 billhorsman
Order allow,deny
Allow from all
Deny from 1.2.3.4

I'm assuming that Apache has already handed over to mod_rails at this point. I can block static files (CSS, etc) but Rails is still called.

Someone is doing repeated searches, several times a second from the same IP. I'd like to stop them doing that :)

Thanks for your help.]]> Blocking an IP Address with Passenger http://forum.slicehost.com/comments.php?DiscussionID=3993&Focus=21618#Comment_21618 http://forum.slicehost.com/comments.php?DiscussionID=3993&Focus=21618#Comment_21618 Mon, 10 Aug 2009 23:35:14 +0000 diazona <Location /> block? If not, I'd put them in one and see if it makes a difference.

:) David]]> Blocking an IP Address with Passenger http://forum.slicehost.com/comments.php?DiscussionID=3993&Focus=21619#Comment_21619 http://forum.slicehost.com/comments.php?DiscussionID=3993&Focus=21619#Comment_21619 Mon, 10 Aug 2009 23:44:53 +0000 billhorsman
Sorry, I should have given more context. I've put them in a <Directory /> block


 <VirtualHost 4.5.6.7:80>
    ServerName www.example.com
    ServerAlias example.com
    DocumentRoot /home/myapp/rails/current/public
    CustomLog /var/log/apache2/myapp.log combined
    RailsEnv production
    <Directory /home/myapp/rails/current/public>
      Options FollowSymLinks
      Order allow,deny
      Allow from all
      Deny from 1.2.3.4
    </Directory>
    RewriteEngine On
    RewriteCond %{HTTP_HOST} ^example.com
    RewriteRule (.*) http://www.example.com$1 [R=301,L]
 </VirtualHost>


Let me see if it works inside a <Location /> block. I'll respond shortly.

-
Bill]]> Blocking an IP Address with Passenger http://forum.slicehost.com/comments.php?DiscussionID=3993&Focus=21620#Comment_21620 http://forum.slicehost.com/comments.php?DiscussionID=3993&Focus=21620#Comment_21620 Tue, 11 Aug 2009 00:00:55 +0000 billhorsman
Yes, that worked :) I now realise the difference between <Directory> and <Location> and took the trouble to read the doc (http://httpd.apache.org/docs/2.2/sections.html).

UPDATE:

To start with, I didn't think it worked - but then I realised I wasn't paying attention to the status code that Apache was serving. Blush. Just to be sure, I switched back to just using <Directory> and discovered that it was working there too (serving up 403 codes). For the record, I guess that "/" works with <Directory> or <Location>.

Thanks for your help and sorry again for not paying attention in the first place.

-
Bill]]> Blocking an IP Address with Passenger http://forum.slicehost.com/comments.php?DiscussionID=3993&Focus=21623#Comment_21623 http://forum.slicehost.com/comments.php?DiscussionID=3993&Focus=21623#Comment_21623 Tue, 11 Aug 2009 03:17:16 +0000 diazona <Location /> is the preferred way to apply a particular directive to everything on the website. (I'm not entirely sure why, but maybe there's a possibility that some URL could be considered not to be in any directory...)

:) David]]>