Just a quick one.
:¬)

I know it's possible to prevent IP addresses from viewing server content
using .htacces, also redirects are possible.
Is it possible to do an ip specific re-direct to an identical looking
site which is not DNS listed? e.g. ip ad. xxx.xxx.xxx.xxx goes to
http://216.71.201.170/discount-cardi...ess-equipment/
instead of
http://www.gymratz.co.uk/discount-ca...ess-equipment/

This is a political issue to do with specific IP's and un-ethical
policies and possible automated spidering that are being used to enforce
illegal pricing policies.

I'd prefer to do this domain manipulation rather than a less subtle
complete content blocking.

Cheers
Pete

--
http://gymratz.co.uk - Best Gym Equipment & Bodybuilding Supplements UK.
http://fitness-equipment-uk.com - UK's No.1 Fitness Equipment Suppliers.
http://water-rower.co.uk - Worlds best prices on the Worlds best Rower.
http://trade-price-supplements.co.uk - Bulk Order Supps. at Trade Prices

"Pet @ www.gymratz.co.uk ;¬)" wrote:

> Just a quick one.
> :¬)
>
> I know it's possible to prevent IP addresses from viewing server content
> using .htacces, also redirects are possible.
> Is it possible to do an ip specific re-direct to an identical looking
> site which is not DNS listed? e.g. ip ad. xxx.xxx.xxx.xxx goes to
> http://216.71.201.170/discount-cardi...ess-equipment/
> instead of
> http://www.gymratz.co.uk/discount-ca...ess-equipment/
>
> This is a political issue to do with specific IP's and un-ethical
> policies and possible automated spidering that are being used to enforce
> illegal pricing policies.
>
> I'd prefer to do this domain manipulation rather than a less subtle
> complete content blocking.

You can do it with PHP or other server-side scripting. For example:

<?php
// Redirect this IP: nn.nn.nnn.nnn
$ipshield = "nn.nn.nnn.nnn";
$visitorip = $_SERVER['REMOTE_ADDR'];
if ($visitorip == $ipshield) {
// do something here
// either redirect or show other content
// use an include statement based on the path requested
exit;
}

If you want to decrease the chance of detection I would show alternate
content rather than redirect. A spider might not follow redirects.


--
http://tips.webdesign10.com/

Pet @ www.gymratz.co.uk <unknown@unknown.gym> wrote:
> I know it's possible to prevent IP addresses from viewing server content
> using .htacces, also redirects are possible.
> Is it possible to do an ip specific re-direct to an identical looking
> site which is not DNS listed? e.g. ip ad. xxx.xxx.xxx.xxx goes to
> http://216.71.201.170/discount-cardi...ess-equipment/
> instead of
> http://www.gymratz.co.uk/discount-ca...ess-equipment/
>
> This is a political issue to do with specific IP's and un-ethical
> policies and possible automated spidering that are being used to enforce
> illegal pricing policies.
>
> I'd prefer to do this domain manipulation rather than a less subtle
> complete content blocking.

I'm not sure wether this is the most efficient way, but hey:

RewriteEngine On
RewriteCond %{REMOTE_ADDR} xxx\.xxx\.xxx\.xxx
RewriteRule ^(.*)$ http://216.71.201.170/$1 [L,R]
--
Rik Wasmus

Rik wrote:
> Pet @ www.gymratz.co.uk <unknown@unknown.gym> wrote:
>> I know it's possible to prevent IP addresses from viewing server
>> content using .htacces, also redirects are possible.
<snip>
> RewriteEngine On
> RewriteCond %{REMOTE_ADDR} xxx\.xxx\.xxx\.xxx
> RewriteRule ^(.*)$ http://216.71.201.170/$1 [L,R]

Thanks Rik.
If there is a block of 8 I.P.'s would I just drop off the last octet
eg. RewriteCond %{REMOTE_ADDR} xxx\.xxx\.xxx
or could I just drop the last 2 parts
RewriteCond %{REMOTE_ADDR} xxx\.xxx\.xxx\.x

Thanks
Pete

Pete @ www.GymRatZ.co.uk <gymratz@biggassmusclebuildingshop.gym> wrote:

> Rik wrote:
>> Pet @ www.gymratz.co.uk <unknown@unknown.gym> wrote:
>>> I know it's possible to prevent IP addresses from viewing server
>>> content using .htacces, also redirects are possible.
> <snip>
>> RewriteEngine On
>> RewriteCond %{REMOTE_ADDR} xxx\.xxx\.xxx\.xxx
>> RewriteRule ^(.*)$ http://216.71.201.170/$1 [L,R]
>
> Thanks Rik.
> If there is a block of 8 I.P.'s would I just drop off the last octet
> eg. RewriteCond %{REMOTE_ADDR} xxx\.xxx\.xxx
> or could I just drop the last 2 parts
> RewriteCond %{REMOTE_ADDR} xxx\.xxx\.xxx\.x

Well, you really should anchor it in that case:
RewriteCond %{REMOTE_ADDR} ^xxx\.xxx\.xxx\.x

Else, for instance, when trying to block 123.456.789.x, you might
accidentally block 321.123.456.789
--
Rik Wasmus

1100000 wrote:

> You can do it with PHP or other server-side scripting. For example:
>
> <?php
> // Redirect this IP: nn.nn.nnn.nnn
> $ipshield = "nn.nn.nnn.nnn";
> $visitorip = $_SERVER['REMOTE_ADDR'];
> if ($visitorip == $ipshield) {
> // do something here
> // either redirect or show other content
> // use an include statement based on the path requested
> exit;
> }
>
> If you want to decrease the chance of detection I would show alternate
> content rather than redirect. A spider might not follow redirects.

Thanks 1100000
I am trying the .htacces route first as it seems easier to do on a
site-wide basis.

Cheers
Pete


--
http://gymratz.co.uk - Best Gym Equipment & Bodybuilding Supplements UK.
http://fitness-equipment-uk.com - UK's No.1 Fitness Equipment Suppliers.
http://water-rower.co.uk - Worlds best prices on the Worlds best Rower.
http://trade-price-supplements.co.uk - Bulk Order Supps. at Trade Prices