Comments on: Want a cookie? http://thenexus.tk/want-a-cookie/ Feed your brain ... Mon, 28 Nov 2011 07:00:25 +0000 hourly 1 http://wordpress.org/?v=3.3 By: Michael Pedzotti http://thenexus.tk/want-a-cookie/#comment-13110 Michael Pedzotti Mon, 24 Jan 2011 13:53:04 +0000 http://thenexus.tk/?p=164#comment-13110 Interesting concept Donace. I am experimenting with a few different techniques without using htaccess. It is proving to be a real challenge but I am enjoying learning more about a few different coding techniques and what I am learning is helping me to improve some functions in my other plugins. Interesting concept Donace. I am experimenting with a few different techniques without using htaccess. It is proving to be a real challenge but I am enjoying learning more about a few different coding techniques and what I am learning is helping me to improve some functions in my other plugins.

]]> By: Update - Links - Love - 2 | The Nexus http://thenexus.tk/want-a-cookie/#comment-13060 Update - Links - Love - 2 | The Nexus Fri, 07 Jan 2011 22:02:52 +0000 http://thenexus.tk/?p=164#comment-13060 [...] about, or just people who like me just want to experiment and speculate have a quick read of ‘want a cookie?‘ that discusses (theoretical) ways to drop cookies, and how to mask the traffic from such [...] [...] about, or just people who like me just want to experiment and speculate have a quick read of ‘want a cookie?‘ that discusses (theoretical) ways to drop cookies, and how to mask the traffic from such [...]

]]> By: Donace http://thenexus.tk/want-a-cookie/#comment-13016 Donace Mon, 13 Dec 2010 21:18:27 +0000 http://thenexus.tk/?p=164#comment-13016 Hey Frank, only quick thing I can think of is use a 1px by 1px ie window to open it up and then close this once an initial load is complete. There probably is an easier way but i'm not a coder so I am probably missing it. though perhaps an embedded ie window/frame on the page to load up the link. Hey Frank, only quick thing I can think of is use a 1px by 1px ie window to open it up and then close this once an initial load is complete. There probably is an easier way but i’m not a coder so I am probably missing it. though perhaps an embedded ie window/frame on the page to load up the link.

]]> By: FrankBlack http://thenexus.tk/want-a-cookie/#comment-13010 FrankBlack Thu, 09 Dec 2010 10:21:16 +0000 http://thenexus.tk/?p=164#comment-13010 Great little tutorial, there is an issue though with this: if(!$_SERVER['HTTP_REFERER']){ It all works great, however if you view source in Firefox then all resources are hyperlinked in the source - and if you click through from the source code then it counts as a referrer and the user will see whatever was meant to be hidden... Any thoughts on this problem? Great little tutorial, there is an issue though with this:
if(!$_SERVER['HTTP_REFERER']){

It all works great, however if you view source in Firefox then all resources are hyperlinked in the source – and if you click through from the source code then it counts as a referrer and the user will see whatever was meant to be hidden…

Any thoughts on this problem?

]]> By: diabolika http://thenexus.tk/want-a-cookie/#comment-3354 diabolika Thu, 09 Jul 2009 15:27:51 +0000 http://thenexus.tk/?p=164#comment-3354 i was looking for how to cook cookies when i fall on this post :D , lol just jocking great post dude :) i was looking for how to cook cookies when i fall on this post :D , lol just jocking great post dude :)

]]> By: Donace http://thenexus.tk/want-a-cookie/#comment-1451 Donace Tue, 04 Nov 2008 16:57:19 +0000 http://thenexus.tk/?p=164#comment-1451 To hide the refer via .htacces is difficult (I dont know how it can be done thus elimating forum cookie stuffing/ image redirects etc). With a php script though what you could do is something like this: <code>BH.com/BHpage1.php -> BH.com/BHpage2.php -> WH.com/Wpage.php -> Affilate page</code> So on your 'BHpage' what it would do is redirect ALL your traffic to the 'wpage' which will drop the cookie and act as your refer. To explain it another way you send 100 visitors to your BHpage (from ANY source) all of these will be redirected to your genuine landing page (i.e. a page that has that affilate links present) These will then fall target to a script as discussed in the article (i.e. a random cookie dropping script). This will result in the Affilate seeing 'wpage' as the referer to all the cookie drops. What this is effect means is you can redirect different traffic sources to BHpage and by tweaking the % on the 'landingpage' drop a fair no of cookies. SO BHpage1= <code><?php echo "<**meta** http-equiv=\"refresh\" content=\"0;url=h**ttp://www.BH.com/BHpag**e2.php\">"; ?></code> BHpage2 = <code> <?php $referer = $_SERVER['HTTP_REFERER']; if($referer == "") { echo "<**meta http-**equiv=\"refresh\" **content=\"0;url=http://WH.com/whpage.php\">"; } ?> </code> Whpage = (see pseduo script in post) This in effect will hide ALL traffic sources and referers and use the 'whpage' as a referer etc. OR an alternative: With the same model above (except with 1 less page) <code>i.e. BH.com/BHpage1.php -> WH.com/Wpage.php -> Affilate page</code> you could use is something like this: <code> <?php $site2 = "http://www.WH.com/Wpage.php"; echo "<**body onload=\"javascrip**t:frmClickTracking.submit();\">"; echo "<**form action=\"" . $site2 . "\**" method=\"post\" name=\"frmClickTracking\">"; echo "<**/form>"; ?></code> <code> <?php $site1 = "http://www.BH.com/BHpage.php"; $affiliate_link = "http://www.youroffer.com"; if($_SERVER['HTTP_REFERER'] == $site1) { echo "<**body onload=\"ja**vascript:frmClickTracking.submit();\">"; echo "<**form action=\"" **. $affiliate_link . "\" method=\"post\" name=\"frmClickTracking\">"; echo "<**/form>"; } ?></code> What the first script does upon landing on the page it redirects the user to your second 'legitmate' page which will then load the affilate page use the 'legitimate page' as your refer. These methods would not as mentioned not work with forum stuffing (as in my knowledge) the refreshes etc will not work though this will work well with CPA offers that limit traffic sources (the second method) or just help you provide more users for your 'cookie script page' (the first method). Also check out <a href="http://www.slightlyshadyseo.com/index.php/controlling-your-referer-and-hiding-your-traffic-sources/" rel="nofollow"> For a bit more info on controlling your referer </a> NB every where you see '**' delete them as they are just there to stop the code being run in the comments To hide the refer via .htacces is difficult (I dont know how it can be done thus elimating forum cookie stuffing/ image redirects etc).

With a php script though what you could do is something like this:

BH.com/BHpage1.php -> BH.com/BHpage2.php -> WH.com/Wpage.php -> Affilate page

So on your ‘BHpage’ what it would do is redirect ALL your traffic to the ‘wpage’ which will drop the cookie and act as your refer.

To explain it another way you send 100 visitors to your BHpage (from ANY source) all of these will be redirected to your genuine landing page (i.e. a page that has that affilate links present) These will then fall target to a script as discussed in the article (i.e. a random cookie dropping script). This will result in the Affilate seeing ‘wpage’ as the referer to all the cookie drops.

What this is effect means is you can redirect different traffic sources to BHpage and by tweaking the % on the ‘landingpage’ drop a fair no of cookies.

SO BHpage1=

< ?php

echo "<**meta** http-equiv="refresh" content="0;url=h**ttp://www.BH.com/BHpag**e2.php">";

?>

BHpage2 =

< ?php

$referer = $_SERVER['HTTP_REFERER'];

if($referer == "")

{

echo "<**meta http-**equiv="refresh" **content="0;url=http://WH.com/whpage.php">";

}
?>

Whpage = (see pseduo script in post)

This in effect will hide ALL traffic sources and referers and use the ‘whpage’ as a referer etc.

OR an alternative:

With the same model above (except with 1 less page)
i.e. BH.com/BHpage1.php -> WH.com/Wpage.php -> Affilate page

you could use is something like this:

< ?php

$site2 = "http://www.WH.com/Wpage.php";

echo "<**body onload="javascrip**t:frmClickTracking.submit();">";
echo "< **form action="" . $site2 . "**" method="post" name="frmClickTracking">";
echo "< **/form>";

?>

< ?php

$site1 = "http://www.BH.com/BHpage.php";
$affiliate_link = "http://www.youroffer.com";

if($_SERVER['HTTP_REFERER'] == $site1)
{
echo "<**body onload="ja**vascript:frmClickTracking.submit();">";
echo "< **form action="" **. $affiliate_link . "" method="post" name="frmClickTracking">";
echo "< **/form>";
}

?>

What the first script does upon landing on the page it redirects the user to your second ‘legitmate’ page which will then load the affilate page use the ‘legitimate page’ as your refer.

These methods would not as mentioned not work with forum stuffing (as in my knowledge) the refreshes etc will not work though this will work well with CPA offers that limit traffic sources (the second method) or just help you provide more users for your ‘cookie script page’ (the first method).

Also check out For a bit more info on controlling your referer

NB every where you see ‘**’ delete them as they are just there to stop the code being run in the comments

]]> By: Chris http://thenexus.tk/want-a-cookie/#comment-1435 Chris Mon, 03 Nov 2008 20:22:04 +0000 http://thenexus.tk/?p=164#comment-1435 Thanks a lot for the reply Donace, I'm currently still tring to make a script or change the .htaccess so that it will hide the referer, having a lot of trouble working out how to do it. I have been pushed in the direction of HTTPS --> HTTP to hide the referer but can't find too much info on the net about it! Thanks a lot for the reply Donace, I’m currently still tring to make a script or change the .htaccess so that it will hide the referer, having a lot of trouble working out how to do it. I have been pushed in the direction of HTTPS –> HTTP to hide the referer but can’t find too much info on the net about it!

]]>