This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Lolu chungechunge lwabekwa kunqolobane. Uyacelwa ubuze umbuzo omusha uma udinga usizo.

Protocol handlers, Firefox 7, linux. What's the story?

  • 3 uphendule
  • 9 zinale nkinga
  • 2 views
  • Igcine ukuphendulwa ngu robblau

Mahlon E. Smith
Mahlon E. Smith
more options

I'm having a hard time Googling for this info, as most of the available information out there appears to be out of date.

Using Firefox 7 on Linux (Fedora 15.) We used to register some custom protocols using gconf, which worked great with Firefox 3. FF7 seems to completely ignore the gconf settings.

Trying to register regular protocol handlers via about:config doesn't appears to do anything, either. This article ( http://support.mozilla.com/en-US/kb/The%20protocol%20is%20not%20associated%20with%20any%20program) didn't help.

What's the correct way to go about doing this now?

I'm having a hard time Googling for this info, as most of the available information out there appears to be out of date. Using Firefox 7 on Linux (Fedora 15.) We used to register some custom protocols using gconf, which worked great with Firefox 3. FF7 seems to completely ignore the gconf settings. Trying to register regular protocol handlers via about:config doesn't appears to do anything, either. This article ( http://support.mozilla.com/en-US/kb/The%20protocol%20is%20not%20associated%20with%20any%20program) didn't help. What's the correct way to go about doing this now?

All Replies (3)

cor-el
cor-el
  • Moderator
  • Top 10 Contributor
more options

See also http://kb.mozillazine.org/Register_protocol

Mahlon E. Smith
Mahlon E. Smith Umnikazi wombuzo
more options

Thanks for your reply.

That's link outlines exactly what I've tried, but isn't working. Trowling through bugzilla shows others with issues (over 100 bugs for a "protocol handler" search), but most are pretty old.

I'm fine with opening a new bugzilla ticket, but I want to try and get a feel for if I've even in the right area still, or if this behavior was long depreciated. I get the feeling that the about:config settings were depreciated in favor of just fallback to the OS (since that worked previously), but that is seemingly ignored now on Linux.

robblau
robblau
more options

Dear people from the future,

There didn't seem to be any good information out there on this and I just had to figure it out. Seems like at some point the about:config tweaks documented all over the place stopped working. The only way I've found to get newer firefox versions to register a custom protocol is to specify a desktop file for the application you want to launch.

The secret sauce is to create a .desktop file in /usr/share/applications for your application (see the existing ones as examples, especially the firefox one for http support). Then add a line to defaults.list (same directory) similar to the other x-scheme-handler lines that are already there, just substitute your protocol and desktop file.

The next time you click on one of the links for the custom protocol you should get the appropriate options to use the registered app to handle the URI.

Okulungisiwe ngu robblau