Network.http.sendRefererHeader

From MozillaZine Knowledge Base

The title given to this article is incorrect due to technical limitations. The correct title is network.http.sendRefererHeader.

This article describes the preference network.http.sendRefererHeader. To add, delete, or modify this preference, you will need to edit your configuration — do not edit this article.

1 Background
2 Possible values and their effects
- 2.1 0
- 2.2 1
- 2.3 2
3 Caveats
4 Recommended settings
5 First checked in
6 Has an effect in
7 Related bugs
8 Related preferences

[edit]

Background

HTTP is the application-layer protocol with which most web pages are transferred. As part of HTTP, requests can include a "Referer" (sic) header that tells the server which page the user was on that initiated the request. Servers use this information to track users' paths through the site and possibly provide additional features.

Additionally, in JavaScript, the current pageâ€™s referrer is exposed in the DOM through document.referrer. Scripts running on the page can consult this property to see the same information that was sent in the Referer header.

This preference controls when to send the Referer header and set document.referrer.

[edit]

Possible values and their effects

[edit]

0

Never send the Referer header or set document.referrer.

[edit]

1

Send the Referer header when clicking on a link, and set document.referrer for the following page.

[edit]

2

Send the Referer header when clicking on a link or loading an image, and set document.referrer for the following page. (Default)

[edit]

Caveats

Disabling Referer headers may cause some functionality on some sites to no longer work.

[edit]

Recommended settings

Those concerned with privacy can set this to 0, realizing that this may adversely affect some sites. Those wanting to ensure compatibility should leave it at the default.

[edit]