The Arcive of Official vBulletin Modifications Site.It is not a VB3 engine, just a parsed copy! |
|
Block User Ip From Your (.htaccess)
Hi All, well all of our forums have some bad members who want to do bad things in our forum so if you want to block him from cpanel he can access again so i thought of this thing blocking Member Ip From (htaccess) file. What Does this do? This Will Block The User IP Or Proxy If You Want From Viewing Your Site. How It Works? Make A New File Using Note Pad and put this code on it: PHP Code:
PHP Code:
PHP Code:
Code:
htaccess.txt Code:
.htaccess Also You Can Add Domains To Block list . Enjoy It |
#12
|
||||
|
||||
Moved to articles section as this isn't actually a vbulletin modification.
|
#13
|
||||
|
||||
Quote:
No problem as I am actually quite happy you brought this topic up. As Forza stated, this really is a subject that needs discussion, since I believe the majority of web admins & owners (at least the ones I know) are running Apache. The links I provided show the various ways that .htaccess can be applied. Maybe a good place to start is the discussion of what does what and where, as my .htaccess code is slightly different, yet both work. To block IPs and IP ranges, Terminatoronly uses... Code:
<Limit GET HEAD POST> order allow,deny deny from 188.156.187.*** deny from 188.155.187.*** allow from all </LIMIT> It appears that he is blocking not just an IP, but an IP range of 188.156.187.0 through 188.156.187.255. If an IP is static (meaning the user's IP does not change - such as most cable & DSL) then one should simply use the specific IP address such as 188.156.187.244. Most "dial up" ISPs use dynamic IPs. Basically meaning that the user is assigned an IP from a block range available from that ISP while logged in. Upon log out, that user relinquishes that IP to the ISP and then it can be assigned to another user within that ISP's range. I know I am probably covering well known knowledge, but sometimes I find that people don't realize just how much banning a block range can effect them and their guests. Banning IP ranges can not only restrict users that may not have done anything to you, but you may also inadvertently knock out search engine spiders, crawlers, good bots, good users, Etc. I really advise against banning IP ranges unless the problem is really that serious, and you have a reasonable idea of just how many other users you may knock out in the process...especially AOL users since AOL routes them through their own proxy servers, and banning even one range of AOL users you can take out a HUGE chunk of other visitors you may wish to have. I use a variation of Terminatoronly's .htaccess file for banning IPs at the server base. For example... Quote:
If someone else wants to hop in and list additional variations (other than mine or Terminatoronly), then please jump on in...as there is ALOT more variations than why are listed so far. Also, here is another variation you might want to try, as it shows how two different uses for .htaccess files can be combined. From my other post I showed you how to block (actually completely redirect ) people linking to your board or site that are not friendly. Code:
Options +FollowSymlinks RewriteEngine On RewriteCond %{HTTP_REFERER} ^http://www.troll_bulletin_board.com RewriteRule /* http://www.malicious_website.org [R,L] RewriteCond %{HTTP_REFERER} ^http://troll_bulletin_board.com RewriteRule /* http://www.malicious_website.org [R,L] Code:
Options +FollowSymlinks RewriteEngine On RewriteCond %{REMOTE_HOST} ^4\.245\.40\.88 RewriteRule ^.*$ http://www.send_them_somewhere_else.net/ [L,R] RewriteCond %{REMOTE_HOST} ^86\.131\.16\.92 RewriteRule ^.*$ http://www.send_them_somewhere_else.com/ [L,R] RewriteCond %{REMOTE_HOST} ^68\.48\. RewriteRule ^.*$ http://www.yahoo.com/ [L,R] RewriteCond %{REMOTE_HOST} ^71\.253\.249\. RewriteRule ^.*$ http://www.send_them_somewhere_else.net/ [L,R] RewriteCond %{REMOTE_HOST} ^68\.114\.48\.210 RewriteRule ^.*$ http://www.send_them_somewhere_else.net/ [L,R] RewriteCond %{HTTP_REFERER} ^http://www.troll_bulletin_board.com RewriteRule /* http://www.malicious_website.org/ [R,L] RewriteCond %{HTTP_REFERER} ^http://troll_bulletin_board.com RewriteRule /* http://www.malicious_website.org/ [R,L] RewriteCond %{HTTP_REFERER} ^http://www.another_troll_bulletin_board.com RewriteRule /* www.another_bad_place.com/ [R,L] RewriteCond %{HTTP_REFERER} ^http://another_troll_bulletin_board.com RewriteRule /* http://www.another_bad_place.com/ [R,L] First, before someone jumps in ans says I should have included "this" or excluded "that" in my .htaccess code above...I am not using the above (or attached) .htaccess file as the "be all and end all" of how to accomplish blocking IPs, IP Ranges, Referral Links, Etc. I am simply showing you one possibility, just as Terminatoronly showed you his variation. I've included a real good beginner's tutorial... http://www.javascriptkit.com/howto/htaccess.shtml as some of the Apache tutorials are about as much fun as watching paint dry. http://httpd.apache.org/docs/1.3/howto/htaccess.html Anyway, I'm sure a lot of Apache users already have a good grounding of what can be done with .htaccess, but maybe some may not be. Also, there are a good deal of variations that can be used for different effects, and I would really encourage Apache users who already use .htaccess to list the way they use them and why. I'll try and pop back in later...but yeah, I think it would be great if people would post their own uses and variations of htaccess files. |
#14
|
||||
|
||||
oh sorry for posting in the wrong section
|
#15
|
||||
|
||||
Quote:
Thanks for the article, btw, I've been scouring the net for articles - and there was a gr8 one here the whole time LoL |
#16
|
|||
|
|||
Quote:
How to redirect banned users (with this method) to an customized error page? Is this possible ? thanks |
|
|
X vBulletin 3.8.12 by vBS Debug Information | |
---|---|
|
|
More Information | |
Template Usage:
Phrase Groups Available:
|
Included Files:
Hooks Called:
|