Ill show you how it works. The main root index.php looks like this (remember I am a novice programmer any improvements please tell me):
<?php
if($cookieblock==goodtogo) header("Location: http://www.t-comuk.net/en/\n\n");
else
header("Location: http://www.t-comuk.net/auth/index.php?pass=******");
?>
The password above is to stop people typing the address into the browser directly bypassing the system.
It checks if you have a “goodtogo” cookie, if not it sends you thought “t-comuk.net/auth” which has a .htaccess file in it to deny access to people I don’t like and don’t wont on the site. Now the clever part is that if you if you reach the blocked page you are permanently denied, as you have cookie set and IP, browser info taken to distinguish you from others.
One problem I had thought was that I am on the same ISP as the ISP I want to block (that’s why I cant just have .htaccess file protecting the hole domain as it would block me as well) it only sends you thought the .htaccess file if you don’t have a cookie so if I manually install the cookie on my machine via my homemade cookie control panel then I bypass the system.
What stops you just typing www.t-comuk.net/en in the browser?? Well there is this line of code in every page in the “en” directory
<?php
include(“basicauth.php”);
?>
Basic auth is a file that’s checks to see if you have a “goodtogocookie” and that you have not had a bar placed against your cookie. When you get a cookie it records your IP address at the time of getting it so when I look at my stats in my homemade cookie manager I can place a block/bar against an IP address then even if they redial it doesn’t matter because the cookie still holds there old IP. It has taken me weeks to do and there are still bugs and improvements to do but its coming along. I am planning on building a system were other sites can join and point the index files at my server it checks fro a blocked ID/Cookie then send them back to the $HTTP_referrer/index2.php.
Thanks, Stu