Network.protocol-handler.external.(protocol): Difference between revisions

From MozillaZine Knowledge Base
Jump to navigationJump to search
No edit summary
 
(→‎Caveats: Linux and Windows -> Linux and Mac)
 
Line 13: Line 13:
*Some protocols cannot be handled internally. Attempting to load a protocol that can't be handled internally does nothing.
*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.
*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 Windows. See [[Register protocol | this article]] for details.
*The external application to run is determined by the OS on Windows and by [[network.protocol-handler.app.(protocol)]] on Linux and Mac. See [[Register protocol | this article]] for details.


==First checked in==
==First checked in==

Latest revision as of 02:03, 18 October 2006

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 should be handled internally or externally.

Possible values and their effects

true

This protocol should be handled by an external application.

false

This protocol should be handled internally.

Caveats

First checked in

2002-03-26 by Patrick C. Beard

Has an effect in

  • Netscape (all versions since 7.0)
  • Mozilla Suite (all versions since 1.0)
  • Mozilla Firefox (all versions)
  • Seamonkey (all versions)

See also

Related bugs

Related preferences