Comments on: Cross domain JavaScript via DNS

By: Kishore Senji

Kishore Senji — Wed, 08 Aug 2007 07:17:20 +0000

They just use an img to track analytics which are sent as request parameters to that gif.

By: Nik Chankov

Nik Chankov — Wed, 08 Aug 2007 06:57:10 +0000

I am wondering how Google analytics make this? They doing for sure because what they do is only contain an Javascript include and an Javascript function and that’s it. After this they collect thatever they can – and they do this. :)

By: iDo

iDo — Wed, 08 Aug 2007 06:28:49 +0000

Jason you also can use a folder…
exemple :
http://www.mydomain.com access to http://www.google.com via http://www.mydomain.com/domain

I use this and it work really good.
I use apache reverse-proxy and cookies are also transmited :)

By: Steven

Steven — Tue, 07 Aug 2007 21:59:03 +0000

This has been used forever in custom advertising relationships (which also avoids new browsers from disabling cookies from third parties).

By: Frank

Frank — Tue, 07 Aug 2007 16:45:13 +0000

Jason,

Check out Abe Fettig’s article on the topic. It’s definitely a step in the right direction!

http://fettig.net/weblog/2005/11/30/xmlhttprequest-subdomain-update/

By: Jason Levine

Jason Levine — Tue, 07 Aug 2007 16:42:59 +0000

This technique seems to require that JavaScript allow passing of information between subdomains. In my experience, Javascript currently doesn’t allow for this to happen. You can’t have x.example.com open an iframe with y.example.com and pass data both ways. (If I’m wrong and there is a way for this to be done, I’d be very interested in it as it would simplify a project I’m working on.)