title: How to set up the Windows registry with a URL-Handler for a custom protocol to invoke Firefox and open a real URL
body: <p>We have a CTI program which uses IE-Framework and opens its content in Internet Explorer.
  We would like to use Firefox instead of IE, but the developers refuse to change anything.</p>
  
  <p>So I thought about an URL-Handler.<br/>
  The CTI-Program uses an URL like <code>https:://software/database/profile=%1.php</code><br/>
  I can tell the program to use a URL-handler.</p>
  
  <p>So the finished URL would look like <code>workaround:https:://software/database/profile=%1.php</code></p>
  
  <p>I made these registry entries: </p>
  
  <p>Windows Registry Editor Version 5.00</p>
  
  <pre><code>[HKEY_CLASSES_ROOT\workaround]
  @="URL:workaround Protocol"
  "URL Protocol"=""
  
  [HKEY_CLASSES_ROOT\workaround\shell]
  
  [HKEY_CLASSES_ROOT\workaround\shell\open]
  
  [HKEY_CLASSES_ROOT\workaround\shell\open\command]
  @="\"C:\\Program Files (x86)\\Mozilla Firefox\\firefox.exe\" "%1"
  </code></pre>
  
  <p>Upon opening <code>workaound:google.de</code><br/>
  Firefox opens infinite numbers of tabs.<br/>
  Same with <code>workaround:"google.de"</code><br/>
  Opening workaround: without anything opens Firefox without a page</p>
  
  <p>Sure, I could add the URL to the registry but the program delivers a variable depending on the database entry of whom is calling.</p>
  
  <p>Does anyone have an idea what parameter Firefox needs?</p>
  
  <p>Thanks in Advance</p>