| Hi,
I made the mistake of using TinyURL.com, a service that claims to "convert long urls into short ones" for one of my mailings.
Now apparently I found that the site does not only convert long urls into short ones, but that BEFORE THE REDIRECTION takes place (from the short tinyurl.com url to the real amazon.com one) the script inserts ITS OWN ASSOCIATE ID BEFORE MINE!
To prove this, I used WGET (a gnu http file retrieval tool for linux and also ported to windows) to do a request to my own "short url".
They cleverly change the redirection address, from what you enter when you create the "tiny url":
www.amazon.com/.../ASIN/BXXXXXXXX/your_associate_id
to
http://www.amazon.com/exec/obidos/redirect?tag=tinyurl-20%rest-of-your-original-associate-url-here
Real URL and associate IDs changed for privacy reasons, the one I'm leaving "as is" is the Tinyurl one!:
c:>wget --user-agent="Mozilla/5.0" http://tinyurl.com/axu6
--05:48:19-- http://tinyurl.com/axu6
=> `yupe6'
Resolving tinyurl.com... done.
Connecting to tinyurl.com[216.234.186.14]:80... connected.
HTTP request sent, awaiting response... 302 Found
Location: http://unicyclist.com/tinyurl/redirect.php?num=axu6 [following]
--05:48:50-- http://unicyclist.com/tinyurl/redirect.php?num=axu6
=> `redirect.php@num=axu6'
Resolving unicyclist.com... done.
Connecting to unicyclist.com[66.98.140.48]:80... connected.
HTTP request sent, awaiting response... 302 Found
Location: http://www.amazon.com/exec/obidos/redirect?tag=tinyurl-20&path=http%3A
%2F%2Fwww.amazon.com%2Fexec%2Fobidos%2FASIN%2FB0000560AA%2Fmyassociateid-20 [followin
g]
--05:48:51-- http://www.amazon.com/exec/obidos/redirect?tag=tinyurl-20&path=htt
p%3A%2F%2Fwww.amazon.com%2Fexec%2Fobidos%2FASIN%2FB0000560AA%2Fmyassociateid-20
=> `redirect@tag=tinyurl-20&path=http@3A@2F@2Fwww.amazon.com@2Fexec@2
Fobidos@2FASIN@2FB0000560AA@2Fmyassociateid-20'
Resolving www.amazon.com... done.
Connecting to www.amazon.com[207.171.182.16]:80... connected.
HTTP request sent, awaiting response... 302
Location: http://www.amazon.com/exec/obidos/ASIN/B0000560AA/myassociateid-20/ [follow
ing]
--05:48:51-- http://www.amazon.com/exec/obidos/ASIN/B0000560AA/myassociateid-20/
=> `index.html'
Connecting to www.amazon.com[207.171.182.16]:80... connected.
HTTP request sent, awaiting response... 301
Location: http://www.amazon.com/exec/obidos/tg/detail/-/B0000560AA?v=glance [fol
lowing]
--05:48:52-- http://www.amazon.com/exec/obidos/tg/detail/-/B0000560AA?v=glance
=> `B0000560AA@v=glance'
Connecting to www.amazon.com[207.171.182.16]:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
[ <=> ] 77,636 20.60K/s
05:48:57 (20.60 KB/s) - `B0000560AA@v=glance' saved [77636]
SO THE COOKIE GETS SET FOR THE ASSOCIATE ID "TINYURL-20" BEFORE it loads the destination page!!.
I wonder what can I do to stop this, and if Amazon.com is aware of this scam. For instance, should associate members be allowed to use the "redirect" url
http://www.amazon.com/exec/obidos/redirect?tag=tinyurl-20&path=http://original-url
???
Second, they are hiding the fact on the tinyurl.com page they they actually REPLACE ASSOCIATE IDs WITH THEIR OWN!!
This, in my view, is a scam!
Create a "tinyurl" for your own original long-url (amazon.com associates individual item view) and see for yourself...
I AM REALLY OUTRAGED!!!
Tinyurl-20 should be suspended!!!! What is an official amazon.com email address to complain about this?
|