Menu:
Subscribe:
Subscribe in a reader
Subscribe to videos only
Subscribe to keli.dk by Email
© 2003-08 Keli Hlodversson
I like browsing the stats for my website. I even take an occasional look at the raw access log.
What I enjoy the most is the list of referring sites, but especially after migrating my site to a weblog system, I've begun seeing a lot of web clients, that abuse the Referer HTTP header to include URLs of pages not linking to my site.
OK web client programmers, here's the relevant section about the Referer header taken from RFC-2616:
The Referer[sic] request-header field allows the client to specify, for the server's benefit, the address (URI) of the resource from which the Request-URI was obtained (the "referrer", although the header field is misspelled.)
Note that it does not say "just put any old URL promoting your software..." It also explicitly forbids including the Referer in requests where the URI was not obtained from a place with an URI:
The Referer field MUST NOT be sent if the Request-URI was obtained from a source that does not have its own URI, such as input from the user keyboard.
Now for the hall of shame. Here's a list of fake referrals I found in my access log:
This is especially irritating as the client fetches the RSS feed quite regularly, and it quickly fills up a spot on my top 10 referrers list with a bogus URL.
Please don't think I'm totally obsessed with standards compliance. But I do think that developers should strive to achieve them whenever possible within reason, and that when they knowingly abuse them is almost unforgivable.
... or maybe I'm just bothered because almost no one links to me, allowing these bogus links to get into my top-ten list. Please post your comments below.