In what cases do browsers really send referrals?

[mikomido]

Obviously when you click a link. And when you otherwise follow a link. Probably when you open a new window/instance/tab. But what about if you type in a new URL in the same tab as you already have a page? What if you go to a bookmark or otherwise invoke a new URL when you already have a page open?

Does it differ between browsers? Can somebody tell me exactly when MSIE, Firefox and Opera send referrals and when they do not (with default configuration)?

[rocknbil]

what about if you type in a new URL in the same tab as you already have a page? What if you go to a bookmark or otherwise invoke a new URL when you already have a page open?

This is a "direct request" and there is no referer.

[tedster]

There was an excellent thread on this topic back in 2002 - it still offers much food for thought.

[webmasterworld.com...]

In that thread, Brett shares these observations

Other things that will throw off referrers:

- some browsers will only send the root domain for any site.
- some browsers and proxy servers will repeatidly send an external referrer for EVERY page it visits. If it comes in from Google, and they visit 20 pages, all 20 pages could see that same google referral string sent.
- Most clued in Opera users turn off referrals as a security precaution. Mozilla may have an option to do the same soon. They are arguing about it now.
- I have heard that there is a version of msn IE that will not report an external referral under some security settings (not sure, but the pattern fits).
- Revisits. If a page is reloaded, some browsers will sent that page itself as the referral. hence, the high proportion of www.mysite.com in your logs.
- no cache mania. Most of the dsl, cable, and other high speed modem manufactuers are telling people to turn off caching in their browser. They all have explicit details on their site as one of the setup steps to take. That in turn is skewing referral numbers as even a simple back button can cause a page reload. That referrer will often be the previous page.

[jdMorgan]

Basically, an HTTP referrer is a page containing the link used to generate the HTTP request. That is, a link that was clicked-on by the visitor, or an included-object link such as <img src="logo.gif"> in the HTML.

So you won't get an HTTP_Referer header for direct type-ins, bookmarks, resources requested by JavaScript, etc. Also, we're talking about browsers here; Many if not most plugins such as media players don't send a referrer either.

Jim

[jomaxx]

FWIW, it used to be the case that Javascript did not send a referrer, but I tested a bunch of different scenarios last year and Javascript almost always sent the referrer page. In fact I'd be interested in knowing if there are any specific exceptions.

One thing I don't think was mentioned yet is that accesses from a local page (i.e. on your C: drive) do not normally send a referrer. I guess it could theoretically be a privacy issue.