Network.protocol-handler.external-default

From MozillaZine Knowledge Base

The title given to this article is incorrect due to technical limitations. The correct title is network.protocol-handler.external-default.

This article describes the preference network.protocol-handler.external-default. 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 See also
7 Related bugs
8 Related preferences

[edit]

Background

Protocols (ex: http, ftp, mailto) are different methods of sending information over the Internet. Protocols may be handled by Mozilla applications themselves, or they may be passed to external applications, or they may not be handled at all. This preference determines whether a specific protocol that is already configured to be handled but whose behavior is not defined by a specific network.protocol-handler.external.(protocol) preference should be handled internally or externally.

[edit]

Possible values and their effects

[edit]

true

This protocol should be handled by an external application. (Default)

[edit]

false

This protocol should be handled internally.

[edit]

Caveats

network.protocol-handler.expose-all or network.protocol-handler.expose.(protocol) (which tell the application that this protocol should be handled in some way) must be set to true for this preference to take effect.
Some protocols cannot be handled internally. Attempting to load a protocol that can't be handled internally does nothing.
This preference only exists by default for certain protocols.
The external application to run is determined by the OS on Windows and by network.protocol-handler.app.(protocol) on Linux and Mac. See this article for details.

[edit]