Implements RFC7252
Also see Copper (Cu4Cr)
Mozilla changed their add-on model to the WebExtensions API, which does not allow implementing protocol handlers.
Copper cannot be fixed to work again unless Mozilla changes the internals of Firefox again -- not to the old one, but a safe one that allows for protocol handler add-ons.
- Copper4Cr: Chrome also uses the WebExtensions API, but has a loophole through discontinued Apps installed in developer mode
- Californium (Cf) Browser: Java-based tool, yet without the debug options support
- Firefox 55 Portable: Downgrade, but only use for add-ons, not browsing...
- Ensure to start offline (no Internet connection!) and disable auto updates
- Open
about:config - Search
browser.tabs.remote.autostartandbrowser.tabs.remote.autostart.2 - Set both to
false
- Get the sources from Github:
clone git://github.com/mkovatsc/Copper.git - Add a text file named
[email protected]to your extension directory of your profile:
- Windows:
C:\Users\<username>\AppData\Roaming\Mozilla\Firefox\Profiles\xxxxxxxx.default\extensions\ - Linux:
~/.mozilla/firefox/xxxxxxxx.default/extensions/ - MacOS:
~/Library/Application Support/Firefox/Profiles/xxxxxxxx.default/extensions/
- Write the path to the Copper sources (i.e., the directory that contains
install.rdfandchrome.manifest) with (back)slash at the end to the file (e.g.,D:\Projects\Git\Copper\). - Since Firefox 43 you need to allow unsigned add-ons by opening about:config and setting
xpinstall.signatures.requiredto false. - Restart Firefox.
- Optionally use about:config with the filter "copper" to clean up old configurations.
Copper should show up in the add-ons list. You can now enter CoAP URIs (e.g., coap://californium.eclipse.org/) into the address bar and will have a user interface to interact with the CoAP resources on a server. The detailed log output is available through the rectangular button on the top right, next to the preferences button.