Søg i 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

custom protocol handler works when clicked, but not when typed into address bar

  • 4 svar
  • 1 har dette problem
  • 4 visninger
  • Seneste svar af rueter

more options

Hi,

I am trying to add a custom protocol handler which would be activated via a right click in the browser (from an online project management software). My current set up is Centos 7 and Firefox 38.7.0 It all seems to work fine with Chrome and/or under OSX but I cannot get this to work on Firefox on Centos 7.

Here is an example: The custom url starts with "rvlink://" and I need the application "RV" to be run when a url like that is passed to the browser.

To get this to work I added the following boolean option in the about:config page:

  network.protocol-handler.expose.rvlink

and gave it the value "false".

Subsequently, when I click a link whos url starts with "rvlink://", Firefox prompts me for the application I would like to use for this type of url, I tell it, remember the choice, and live happily ever after. However, when I type the custom url into the address bar or call it via a right click menu (which it ultimately needs to be run from), Firefox errors saying "The address wasn't understood".

When I create al ink and click that first to teach Firefox about the custom url, then the other options seem to work as well. But it has to be a link the first time it would seem.

What's the difference between clicking a link and calling the same exact url via a right click menu or typing it into the address bar? And what do I need to do to make it behave consistently?

Thanks in advance,

frank

Hi, I am trying to add a custom protocol handler which would be activated via a right click in the browser (from an online project management software). My current set up is Centos 7 and Firefox 38.7.0 It all seems to work fine with Chrome and/or under OSX but I cannot get this to work on Firefox on Centos 7. Here is an example: The custom url starts with "rvlink://" and I need the application "RV" to be run when a url like that is passed to the browser. To get this to work I added the following boolean option in the about:config page: network.protocol-handler.expose.rvlink and gave it the value "false". Subsequently, when I click a link whos url starts with "rvlink://", Firefox prompts me for the application I would like to use for this type of url, I tell it, remember the choice, and live happily ever after. However, when I type the custom url into the address bar or call it via a right click menu (which it ultimately needs to be run from), Firefox errors saying "The address wasn't understood". When I create al ink and click that first to teach Firefox about the custom url, then the other options seem to work as well. But it has to be a link the first time it would seem. What's the difference between clicking a link and calling the same exact url via a right click menu or typing it into the address bar? And what do I need to do to make it behave consistently? Thanks in advance, frank

Alle svar (4)

more options
more options

Hm. That's a bit vague. You just pointed me to the main page of the developer docs. I found the haystack now, but where is that needle...

more options

2nd bullet item on that page:

http://stackoverflow.com/questions/tagged/firefox+or+firefox-os+or+html5-apps+or+firefox-developer-tools

more options

I see. You were telling me to post in a more appropriate place. Sorry, that wasn't clear to me at all. Will do, thanks