For example, if I enter
steam://connect/127.0.0.1 in the Omnibox, it will search for the URL instead of launching the program that handles that protocol.
How can Chrome be configured to treat custom protocols correctly?
Super User is a question and answer site for computer enthusiasts and power users. It only takes a minute to sign up.Sign up to join this community
This can be adjusted in Chrome's
Local State file.
The exact location depends on your OS. For example:
%LOCALAPPDATA%\Google\Chrome\User Data\Local Stateon Windows 7.
~/Library/Application Support/Google/Chrome/Local Stateon Mac OS X 10.8.
~/.config/google-chrome/Local Stateon Ubuntu 12.04.
Close Google Chrome.
Local State file and search for
Add the line
Restart Google Chrome.
As a reference it looks like Custom URIs not being followed in the Omnibox or when passed as a command line parameter is known issue 560809 in Chromium.
As of writing the issue does not describe any workarounds :/