Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- Exclamation HTAccess help needed Part 2 (now urgent)
- I previously sought advice about this issue in the following thread;
- ++++++++++++++
- list of top cheapest host http://Listfreetop.pw
- Top 200 best traffic exchange sites http://Listfreetop.pw
- free link exchange sites list http://Listfreetop.pw
- list of top ptc sites
- list of top ptp sites
- Listfreetop.pw
- Listfreetop.pw
- +++++++++++++++
- https://www.webhostingtalk.com/showt...230&p=10138955
- I was given the following code to try to achieve an effective block on websites referring people I am trying to prevent seeing my website - in particular one person who is a threat to me and to the community I represent;
- Code:
- RewriteEngine on
- RewriteCond %{HTTP_REFERER} newipnow\.com [NC,OR]
- RewriteCond %{HTTP_REFERER} hidemyass-freeproxy\.com [NC,OR]
- RewriteCond %{HTTP_REFERER} translate\.googleusercontent\.com [NC,OR]
- RewriteCond %{HTTP_REFERER} archive\.org [NC]
- RewriteRule .* - [F]
- Now in the last few minutes I checked on Stat Counter and discovered that the first block - for newipnow.com - didn't work as another person who is a threat to me used it and was able to access my website despite the above code in my HTAccess. This second person is a bigger threat to me because he has threatened to kill me in the past (and the police believed he was bluffing to my total fury).
- So this is now urgent. How do I fix this on my HTAccess file and make sure it actually works? I'm desperate here.
- Many reasons "REFERER" might be bypassed or simply not work.
- Maybe this will help you get on the right road:
- https://forums.cpanel.net/threads/ht...31/post-300623
- make money kh3
- www.trinityfunnelsystem.com
- cloudcone.com
- seastarhits.com
- domain and range
- secure.hostgator.com
- 10buckblast.com
- e host morgan
- Show your support for everyone affected by the Australian bush fires, and those fighting them
- Not really, because the code suggested is what I am already using for IP deny - and at times even that hasn't worked.
- I am interested though in this comment; "One very easy thing to do is just simply drop all connections that have an "X-Forwarded-For" variable set and this kind of block can be setup easily in .HTACCESS."
- From what was said, this is what most proxies use and would be useful. So how would I do this?
- Not really, because the code suggested is what I am already using for IP deny - and at times even that hasn't worked.
- Looks like you missed the rest of that block and only saw the IP?
- <Files *>Order Allow,Deny
- Allow from all
- Deny from 10.1.3.0/24
- Deny from hidemyass.com
- deny from proxy.com
- deny from anonymouse.com
- deny from proxify.com
- </Files>
- Show your support for everyone affected by the Australian bush fires, and those fighting them
- No I didn't miss that. "Deny from" hasn't been working for IP's at times so why would it work for websites that I'm already having issues with too? That's what I meant.
- Could you show me that other coding I asked about?
- I confirmed the rewrites do block if they have the keywords in the referer header. So what does the referer in a log file show? Is the user agent used an actual browser or something else obvious like "newipnow-proxy"? Again both coming from the apache log files and not scripts. A few log entry examples of those that shouldn't not have access may help.
- -Steven | u2-web@Cooini, LLC - Business Shared Hosting | Isolate sites with Webspaces | Site Builder | PHP-FPM | MariaDB
- WHMCS Modules: Staff Knowledgebase | Custom Modules and Hooks
- I previously sought advice about this issue in the following thread;
- https://www.webhostingtalk.com/showt...230&p=10138955
- I was given the following code to try to achieve an effective block on websites referring people I am trying to prevent seeing my website - in particular one person who is a threat to me and to the community I represent;
- Code:
- RewriteEngine on
- RewriteCond %{HTTP_REFERER} newipnow\.com [NC,OR]
- RewriteCond %{HTTP_REFERER} hidemyass-freeproxy\.com [NC,OR]
- RewriteCond %{HTTP_REFERER} translate\.googleusercontent\.com [NC,OR]
- RewriteCond %{HTTP_REFERER} archive\.org [NC]
- RewriteRule .* - [F]
- Now in the last few minutes I checked on Stat Counter and discovered that the first block - for newipnow.com - didn't work as another person who is a threat to me used it and was able to access my website despite the above code in my HTAccess. This second person is a bigger threat to me because he has threatened to kill me in the past (and the police believed he was bluffing to my total fury).
- So this is now urgent. How do I fix this on my HTAccess file and make sure it actually works? I'm desperate here.
- Use a provider that can give you access to a CDN that can just block entire countries.
- Akamai does this well and you can block entire IP ranges.
- But you need to block all VPN ports as well.
- Just blocking single IP addresses is pointless as they can get new ones easily.
- If privacy is that important you are probably better off hosting your stuff on a private cloud and allowing access to designated IPs.
Advertisement
Add Comment
Please, Sign In to add comment