Quote:
Originally Posted by Squirtit
I mean setting a cookie for surfers sent by a Verotel affiliate.
Instead of making a copy of my site for Verotel, when the Verotel affiliate surfer clicks join, the cookie is read, and they are sent to the Verotel signup page, instead of CCBill 
|
Forget it!
You can't read the verotel cookie!
PERIOD!
The best you could do is make a verotel landing page that, when loaded, gives the
surfer
your cookie that says "surfer=verotel".
But that means having a separate tour page which is exactly what you don't want to do.
So go ahead and copy the pages like I said because you are going to copy the page
no matter what you do.
Think about this :
What if you could read the verotel cookie on your site? Then you could also read
the surfer's bank cookie on your site.
And since that surfer was logged into his bank when he surfed your site
and his bank is using a cookie session to log the surfer into his account, you would be
able to read his cookie and create that cookie on your browser and then go to his
account and steal all of his money.
That doesn't happen because the surfer's browser will only send the bank's cookie to
the bank's domain.
Now. Don't make me come back into this thread again!