Exact URL matching + Port number matching filters for credential list

+1 on developing better matching of URLs, it would be great if there was a way to say in an item "match exactly", and/or to add to the smarts of URL matching so that it prioritises or weights the matches according to how close a match they are.

I have one particular use case where this would be useful, which is a website that has a secondary auth with a different password needed on a specific page to do a specific thing.

In that item, I have that specific URL in there, however that item still shows up as recommended, along with the primary one, for all auth instances on that site. Whilst it's only two entries and fairly easy to choose the right one, it would be good if it would recognise the exact match and only show that result.

:+1: for this as well from my side.
Currently it does not seems to be working (Chrome plugin version 2.1.4, 1Password 7 Version 7.9.2 , 70902005)
It is very helpful to distinguish between subdomains and port numbers and filter based on exact url match as we might end up having 8+ suggestion items without prefiltering.
We happen to have several times different on some pages, which share the same top level domain(netflify, github pages, also works like this ).

I also saw several previous closed with similar request in the past for browser suggestion filtering since 2015.

Was there a progress with this previous request, and may we know when it might be shipped into the browser extension?
Thanks

I know the topic has already been addressed, but I have read so many threads with this request and the answer is always the same: "Thank you for the feedback"; "We hope to improve and expand this feature in the future", and so on. There are requests that are years old and recent requests and there is still no news about them. At the moment 1password sorts suggestions like this:
1) Favorites that contain the same domain.
2) Exact matches of the subdomain + domain.
3) Matches of the domain (but can be different subdomains or suffix / prefix in the URL).
Leaving aside the favorites, what many users are asking is to have a flag that suggests only the second case, hiding the third (possibly on the single item and not just as a global parameter).
Is this kind of change really on the roadmap, as you keep saying?

Thanks for an honest answer

1Password Version: 80500065
Extension Version: 2.2.0
OS Version: Windows 10

Thanks for answering

Consider this an up-vote from me! I fully agree with this request.

This would help me personally with my bank, where I have multiple unrelated accounts. One banking portal uses a different subdomain host address, the other uses a different path.

This would also help in a dev/test/prod situation, especially since Display in browser has been removed. :-/

@Dave_1P and @Jack.P_1P, Thanks for update! I am glad to hear that feedback from the users has gone back to the devs. Hopefully the requested functionality makes its way in to the product.

Sorry for the double post. I think the second one got help up in the post review process and then added to this thread when it was approved.

I know you're still working through the sub/root domain request everyone here wants but is there an update to the sorting of the inline menu as mentioned in #Comment_619254

Yes. There is a sorting mismatch between the inline menu and the toolbar button.

The inline menu is not correct. The toolbar menu is.

Email sent as requested. The support ID is #IMV-32471-446

A very common case now is redirects for auth. Authelia for example as it is usually set up behind nginx will redirect to site/authelia. The authelia login entries show up on every site. Since in my case "site" is also a wild card cert with about 15 different entries, I get a massive list of possible matches using the current 1password behavior. It's not terrible on the desktop because there is enough info to choose the right one, but on IOS the list only shows username and the domain but not the subdomain. The list makes it impossible to choose the correct entry, this is a serious usability issue on IOS. You really should show the subdomain.domain for the entry. What I'd really like is "match on url" as an option for these authelia entries and "match on subdomain.domain only" as an option for these wildcard cert entries. Then it would prompt me with the correct choice.

Hi, Ive specifically signed up / made an account to chime in on this ( IE: +1 for better/full URL matching, in my case Especially differentiate PORT numbers in URL matching, ie 192.168.1.1:3040 is different than 192.168.1.1 and different from 192.168.1.1:3041).

As many have pointed out, im in the same boat in that i get MANY 1pw suggested autofill options, usually based only on the IP address (root domain, in the case of an IP). As a network admin and coder, you can imagine i frequently access non-public, unusual URLs , daily.

Ive read all the technical replies in regards to, hashing of the saved creds entry and comparing that to a hash of the current site root/sub-domain hash = match or no-match -> however i dont understand why this same process could not work for a hash of the full url (or a hash of root domain and also a 2nd hash of root-domain + port number) vs the same 2x hashes saved at cred creation/in 1pws database. I dont really need an answer to this question, i just REALLY need this to be fixed, as in general i get way too many, "generic" 1pw autofill suggestions for a 40% or so of the login/pass fields i click on. (win11, chrome or FF, 1pw v7).

another question im putting out there (does not need an answer), why is necessary for the URLs of saved credentials to even be encrypted in the first place? (i agree, yes, it is better for entire entry to be encrypted, but if the exact URL of xyz stored cred kept in a UN-Encrypted state FIXES this issue, i am fine with that).

or even better: give the user the option. IE: by default all is encrypted, but optionally (if you need/desire more precise matching of full-URL->autofill suggestion, then you can OPT IN/enable to have all stored URLs kept un-encrypted.
ie something like:

(stored in) CLEARTEXT: "admin.mydomain.com:4500" is LINKED to ENCRYPTED: credentials "bob/myPW ect.." so match fully/accordingly when 1pw browser extension hits a login/pw field.

thanks!

Has this regressed in 1Password 8? The filter in Quick Access is clearly based on the publicsuffix+1 and the sort is simply alphabetical on name. I don't care so much about the filter excluding things, but it is a gigantic pain in the butt to be constantly getting the password for my printer recomended for my NAS, router, etc. simply because Canon starts with "C" and the other brands come later in the alphabet.

+1 1Password engineers -- please fix this at long last. Things actually got worse in this regard with 1P8. :-(