Exact URL Matching please

[MarkCanada]

I am running into issues where username/password fields are being filled out on pages that shouldn't be.
If you have for example a WordPress website with WooCommerce you use KeePass to store the login credentials.
The problem is that if for example you have Paypal Express Checkout installed and you go to configure it the username and passwords fields are being filled in with the WordPress login information.
The problem is that if you have stored correct information and you switch to this then the username/password of the PayPal API are overwritten with your WordPress credentials.
I just came across https://www.kee.pm/ for FireFox which adds additional settings to each KeePass entry. One of them being "Exact URL match". By selecting this on the WordPress login page entry for the site it keeps it from destroying other username/password fields like the above in the admin area.
It would be great if keepasshttp could do the same so I can use it in ChromeIPass and don't have to keep disabling the plugin or create multiple entries to stop auto-entry.

[breytex]

+1
have the exact same issue with plesk.
When adding another e-mail-adress, the fields get filled out with the plesk credentials.
Please add exact domain matching.

[scrobbleme]

+1 Have the same issue, this is a quite dangerous behaviour.

[YiiRocks]

+1 https://plesk_server:8443/login_up.php could be matching that page only, but currently I don't have that option.

[fr-nk00]

+1 This behaviour is absolutely critical when you're working with user accounts admin and things like that. I don't want my own login credentials to be filled in everywhere!

When I fill in a very strict url in KeePass, I'd expect only that url to be matched. I made it strict on purpose.

[christianschneider89]

+1