Forum Moderators: phranque
We have tested this on multiple machines. The same machines visiting the site from Google or Yahoo search have the referrer.
Anyone else seeing this?
<a href="http://www.example.com/" gping="/GLinkPing.aspx?/_1_9SE/1?http://www.example.com/&&DI=293&
IG=aeda64ef9eb548638565d31309e0e1f1&POS=1&CM=WPU&CE=6&
CS=AWP&SR=6&sample=0">example</a></h3> (Carriage returns added for clarity, some details obfuscated)
If you enable referers in the browser and click the link, you can record the HTTP headers. You see something like this:
http://search.msn.com/GLinkPing.aspx?/_1_9SE/1?http://www.example.com/&&DI=293
&IG=aeda64be9eb548638565d31309e0e1f1&POS=1&CM=WPU
&CE=6&CS=AWP&SR=6&sample=0
GET /GLinkPing.aspx?/_1_9SE/1?http://www.example.com/&&DI=293
&IG=aeda64be9eb548638565d31309e0e1f1&POS=1
&CM=WPU&CE=6&CS=AWP&SR=6&sample=0 HTTP/1.1
Host: search.msn.com
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.5) Gecko/20060731 Ubuntu/dapper-security Firefox/1.5.0.5
Accept: image/png,*/*;q=0.5
Accept-Language: en-ca,en;q=0.8,fr-ca;q=0.5,fr;q=0.3
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 300
Connection: keep-alive
[b]Referer: ht[/b][b]tp://search.msn.com/results.aspx?q=example&FORM=QBHP[/b]
Cookie: [i](removed)[/i]
[b]HTTP/1.x 200 OK[/b]
Content-Length: 42
[b]Content-Type: image/gif[/b]
X-Powered-By: ASP.NET
P3P: CP="NON UNI COM NAV STA LOC CURa DEVa PSAa PSDa OUR IND", policyref="http://privacy.msn.com/w3c/p3p.xml"
X-TraceID: b1f123f02fac4849968f6212fef11b81
Expires: Sat, 09 Sep 2006 17:52:06 GMT
Cache-Control: max-age=0, no-cache, no-store
Pragma: no-cache
Date: Sat, 09 Sep 2006 17:52:06 GMT
Connection: keep-alive
----------------------------------------------------------
http://www.example.com/
GET / HTTP/1.1
Host: www.example.com
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.5) Gecko/20060731 Ubuntu/dapper-security Firefox/1.5.0.5
Accept: text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
Accept-Language: en-ca,en;q=0.8,fr-ca;q=0.5,fr;q=0.3
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 300
Connection: keep-alive
HTTP/1.x 200 OK
Date: Sat, 09 Sep 2006 17:52:07 GMT
Server: Apache
Last-Modified: Sun, 03 Sep 2006 21:17:51 GMT
Etag: "2860310-bca-44fb467f"
Accept-Ranges: bytes
Content-Length: 3018
Keep-Alive: timeout=15, max=100
Connection: Keep-Alive
Content-Type: text/html At the moment, I'm not entirely sure what the GLinkPing.aspx script is doing, but it declaring a MIME type of
- it is actually a 1x1 pixel transparent GIF image rather than a HTML document. A tracking beacon, maybe, which remains in the browser cache? As you can see, the image/gif
gping attribute is working as an onclick event, overriding the link. Once the image script is fetched, there is a redirect to the chosen website - but in Firefox (and thus in other Gecko-based browsers), the referer information is not included in the second request. As there is no 301 or 302 redirect (only a 200 OK for GLinkPing.aspx), perhaps Gecko doesn't realise that it should pass on the information to the landing page? Perhaps the image MIME type is confusing things?
Does anyone get any referers from MSN Search from Gecko browsers (Firefox, etc.)? If referers are never passed, then we may be underestimating the number of visitors coming from MSN - even if you consider the probability that most MSN Search users are connecting with Internet Explorer.
I see some Gecko requests with a MSN referrer, but they are rare.
Likewise. Can you supply any of the exact UA fields? I got none in September and a grand total of 3 in August:
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.5) Gecko/20060719 Firefox/1.5.0.5
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.6) Gecko/20060728 Firefox/1.5.0.6
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1b1) Gecko/20060710 Firefox/2.0b1
And yet, I was able to immediately produce a hit with a Referer field from MSN search myself:
Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8.0.6) Gecko/20060728 Firefox/1.5.0.6
I guess it's possible these results are accurate for my site. About 2/3 of my total page hits from Gecko browsers are claiming revision 1.8.0.6. Hmm.
"Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.6) Gecko/20060728 Firefox/1.5.0.6"
I tested search.msn.com, search.msn.co.uk and search.msn.com.my and all of them are the same.
I'm more annoyed by the fact that Firefox is incompatible with the MSN-based official website for Rock Star: Supernova (a guilty pleasure). You'd think that, after ten years of this, these companies would have grown up and stopped victimizing the public by deliberately creating broken websites that force you to switch browsers or upgrade your plug-ins.
I'm sure my ranking is still good even on the new engine, but very few referrals from msn.com or search.msn.com in the last 2 or 3 days.
Today, absolutely zero.
and: I also see the code
<a href="http://www.example.com/" gping="/GLinkPing.aspx?/_1_9SE/1?http://www.example.com/&&DI=287&IG=088748d6etc.">
Surely this is connected to the g.msn.com/9SE/1?http://www.domain.com that we have been seeign in the logs in the last few months.
I guess this is not technically "a cookie" but "a way to track this search and this click" in the neural approach that MSN seems to be using 100% now...
1st consequence: yes, MSN has the right to do whatever they want, but the trackign of live.com searches is totally unpredictable
2nd consequence: I'm waiting for my ranking to increase soon as I'm deeply convinced that with the neaural component our sites will gain positions :-)
There is a post around here somewhere from about 3 years ago where I proposed that SEO would be finished if engines switched from GET to POST.
Anyone know the url? It was something like "seo, three chars from done" or something like that. Erm, was it in supporters?
However, lets be honest, they don't have the guts to do it on the organic side (too much value in the self promotion involved) and they also need to be able to have advertisers see those referrals on the paid side.
Anyway, in another thread [webmasterworld.com], MSNdude says about the missing referrer: "This is NOT by design. We're looking into it. Thanks for telling us."
If you are a supporter:
[webmasterworld.com...]
window.location = _pendingAddress;
so it depends on how the browser handles this command, in most cases no HTTP_REFERER is set I suppose
they are handling opening the page in new window separately, in such case the HTTP_REFERER should be passed
It's not enough to be doing something for another business. In order for your to thrive, the other business must also KNOW you are doing it. And webmasters tend to be heavy influencers of tech use among their circle of contact. That's how Google got off the ground -- the tecchies spread the word. Live could eventually spread through the entire culture of web users in the same way, but only if webmasters actually see the results.
I'm sure MSN will not let this stand.