I wanted to block or redirect certain IP address and ranges... from seeing my lander...
Can you do something like this in STATIC CDN? Does static CDN like (RACKSPACE) make this work? or I have to switch my lander back to my server?
Also..
Can you guys help me create a good...
.htaccess that redirects 123.123.123.*
from accessing www.myoriginallandingpage.com and redirect the IP 123.123.123.*
into
www.myfakelandingpage.com
I already tried searching google... and couldn't some up or create one... 
rackspace told me no when i asked them about this
Htaccess files are interpreted by web servers and primarily used by Apache.
Since CDNs aren't traditional web servers, no, they won't be influenced at all by htaccess files - this would be a massive liability as well as it would give end users the ability to manipulate the CDN behaviour.
Your best bet is to
a) use a tracking system to do this before anyone gets to the lander
b) use PHP thus have the page on your server.
Option b) is more useful as a) only stops people getting there if through your tracking link - once they find the lander it's over. Javascript won't be able to help you hide things here from someone with any know how.
Hi guys...
Thanks for the reply...
@Zeno
I am using
I just went to browse my
You can't add IP-based rules yet. If you know of some specific thing you want to redirect, isolate it down to a specific carrier or ISP and user-agent combo.
yeah... I went ahead and tried ISP... and I think it did not work out... lol... or maybe the traffic source staff have many other ISP...
coz my account in the traffic source got suspended... for using interrupt or exit-pop script on my lander...
Were you actually using those? If you were hoping to dodge non-compliance... I don't think a simple redirect rule is a good solution.
Yeah I tried using the RULE...
and setup...
*MUST BE* (ISP)
so if the ISP is detected it goes into a secondary path... if the ISP is not detected it will go to a lander with interrupt/pop script...
I mean, were you actually using the interrupt/pop script, which is not compliant.
If so, the obvious thing to do is not have this in your funnel at all during ad approval. If you add it later, be content with the fact you may get caught and/or get kicked off the traffic source.
Risk/reward.