Gecko.handlerService.allowRegisterFromDifferentHost

From MozillaZine Knowledge Base

The title given to this article is incorrect due to technical limitations. The correct title is gecko.handlerService.allowRegisterFromDifferentHost.

This article describes the preference gecko.handlerService.allowRegisterFromDifferentHost. 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 True
- 2.2 False
3 Caveats
4 First checked in
5 Has an effect in
6 Related bugs
7 Related preferences
8 External links

[edit]

Background

Firefox 3 allows web pages to register themselves as protocol handlers. This allows, for example, all links starting with mailto: to be sent to a webmail provider, or all links starting with webcal: to be sent to an online calendar site. The information on these registrations is kept in mimeTypes.rdf

To prevent websites from registering handlers for other sites and then stealing information meant for the other site, Firefox requires that the host of the URL used by the protocol/content handler matches the host of the site from which the user installs the handler.

[edit]

Possible values and their effects

[edit]

True

Allow sites installing protocol/content handlers to use URLs with different hosts in the handler

[edit]

False

Require sites to use hosts matching the current site in protocol/content handlers (Default)

[edit]

Caveats

This preference controls behavior designed to prevent malicious websites from intercepting data sent with protocol handlers. You should set this to true only if you are aware of the security impliciations.

[edit]