KeePass / Discussion / Open Discussion: Scheme-specific URL overrides

Dominik Reichl - 2009-07-17

For KeePass 2.09, I've added scheme-specific URL overrides, i.e. overrides that only apply to URLs with a specific scheme (like http, https, ssh, ...). This way you can for example tell KeePass to open all http- and https-URLs with Firefox or Opera instead of the system default browser (KeePass 2.09 will ship with appropriate overrides, which however are disabled by default). PuTTY is set as handler for ssh-URLs by default. See Options -> Integration.

The latest 2.x development snapshot for testing is available here:
http://keepass.info/filepool/KeePass_090717c.zip

Extensive testing and feedback is very welcome :-)

Thanks and best regards
Dominik

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- Kev - 2009-07-18
  
  This is a really nice idea. :-)
  
  Just wondering if it would be possible to have a {GOOGLECHROME} placeholder. Or even the ability to create your own placeholders?
  
  Thanks.
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- Dominik Reichl - 2009-07-18
  
  Well, with field references you already can realize database-global placeholders, of course they don't look that nice (like {REF:U@T:Google Chrome}, where an entry with title 'Google Chrome' contains the path in the user name field). Or you could use environment variables (enclosed in '%'s).
  
  Adding a placeholder for Google's Chrome is a great idea, I'll have a look at that.
  
  Thanks and best regards
  Dominik
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- Kev - 2009-07-18
  
  Thanks for considering the Google Chrome idea.
  
  :-)
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- Dominik Reichl - 2009-07-18
  
  I've implemented the {GOOGLECHROME} placeholder (I've used your suggestion instead of just {CHROME}, in order to avoid confusion between the Chrome engine of Firefox and Google Chrome).
  
  An appropriate entry for Google Chrome is also available in the URL scheme overrides dialog. Additionally, I've added an item for the chrome scheme used within Firefox (thanks luckyrat :-) ).
  
  The latest 2.x development snapshot for testing is available here:
  http://keepass.info/filepool/KeePass_090718b.zip
  
  Thanks and best regards
  Dominik
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Dave - 2010-01-01

I use KeePass 1.17 and have Google Chrome installed. But {GOOGLECHROME} used in the URL does not work as it appears to be empty. How do I get KeePass to recognize and set the path in {GOOGLECHROME}?

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Paul - 2010-01-01

The place holder is only in the V2 snapshot.

cheers, Paul

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Dave - 2010-03-17

Paul, if {GOOGLECHROME} is only a V2 feature, then why is it listed in the KeePass Auto-Type description at
http://keepass.info/help/base/autotype.html as available in both V1 and V2, i.e. it is NOT listed in the KeePass 2.x Only section.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Paul - 2010-03-17

Sorry, I misled you. It was only in the V2 snapshot in July last year. It's now in V1 as well.

cheers, Paul

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Dave - 2010-03-18

Well, I'm glad it's in Version 1.17 but it still comes up null for me. I have KeePass 1.17 on both my laptop and my desktop, both machines are XP Home SP3. Google Chrome runs fine on both machines but, for reasons I don't understand, Google Chrome is installed in different directories:

Laptop: "C:\Program Files\Google\Chrome\Application\chrome.exe"

Desktop: "C:\Documents and Settings\Davit\Local Settings\Application Data\Google\Chrome\Application\chrome.exe"

But the problem is that {GOOGLECHROME} comes up null (empty) on both machines, hence I can't use it. Why doesn't 1.17 recognize the directory?

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Dominik Reichl - 2010-03-18

You're right, the installer of Google Chrome in the meanwhile creates different registry keys; the install path can't be found at the previous place. I've now added support for also detecting newer versions of Chrome (for both 1.x and 2.x; this wasn't a 1.x-only issue).

Here are the latest development snapshots for testing:
KeePass 1.x: http://keepass.info/filepool/KeePass_100318.zip
KeePass 2.x: http://keepass.info/filepool/KeePass_100318b.zip

Thanks and best regards
Dominik

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Dave - 2010-03-18

Thanks, Dominik. The development snapshot for KeePass 1.x worked fine on both machines where Google Chrome was installed in different directories.

I am, however, curious as to the difference in keepass.exe sizes. The released version is 755 KB and your snapshot is 1744 KB. Why such a big difference?

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Dominik Reichl - 2010-03-18

Development snapshots are always larger than official releases for various reasons (no UPX compression, eventually containing debug information, …), that's normal.

Best regards
Dominik

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Dave - 2010-03-18

OK, thanks for the information and the fix! Will look forward to the release of Version 1.8 (or whatever you call it).

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Scheme-specific URL overrides

A lightweight and easy-to-use password manager

Forums

Help

Scheme-specific URL overrides

Scheme-specific URL overrides

A lightweight and easy-to-use password manager

Forums

Help

Scheme-specific URL overrides document.SUBSCRIPTION_OPTIONS = { "thing": "topic", "subscribed": false, "url": "subscribe", "icon": { "css": "fa fa-envelope-o" } };

Scheme-specific URL overrides