Bug report: URL matching in 1P6 extension does not behave like the MacOS or 1P4 Windows versions

kop48

I had my Apple login item configured to http://*.apple.com - this fills correctly on every other device, BUT the 1Password for Windows 6 browser extension. I had to modify the URL to exactly match the Apple site that I was trying to auto-fill my login for. Any reason why this has changed?

---

1Password Version: Not Provided
Extension Version: Not Provided
OS Version: Not Provided
Sync Type: Not Provided

matthew_ag

[Edited]

Hi @kop48,

Thanks for writing in! Unfortunately 1Password for Windows 6 support that kind of website address (including an asterisk wildcard) as you have found and I can't say that it will in the future. I'm sorry about the inconvenience.

However you've also found the alternative way to get this to work - simply edit the website field to match the website you need to log into. In most cases the sub-domain part of the URL is ignored when Login items are being searched for during matching. So for example, if you were on "https://appleid.apple.com" but had "https://www.apple.com" in your website field, then that Login item will still appear when you click the 1Password extension button.

I hope this helps - if you've any further questions or something doesn't makes sense don't hesitate to let me know.

Best regards,
Matthew

kop48

I'm sorry to hear that it's not backwards compatible. Thankfully, the fix is permanent and only encountered once per affected domain.

matthew_ag

Sorry for the inconvenience @kop48 , hopefully you don't have too many to change. Thanks for letting us know!

littlebobbytables

Hi @kop48,

I just want to expand a bit on what's already been written as I think there's some confusion. To the best of my knowledge no version of 1Password supports wildcards in URLs, instead what you're seeing is a different piece of behaviour that is present. When 1Password attempts to match a Login item it first looks at the FQDN (Fully Qualified Domain Name). If it doesn't find a match it will strip away any subdomains and look at just the registered domain and see if there is a match. It means *.apple.com behaves the same as www.apple.com as 1Password first notes that *.apple.com != www.apple.com but that apple.com == apple.com. Another key different is the latter could be used for open and fill. I would probably go with setting it to https://appleid.apple.com as that's the page they use.

I believe there is some work needing done in 1Password 6 for Windows in terms of comparing not just the FQDN but also the registered domain but we don't support regex in URLs or the exception list for autosaving.

kop48

@littlebobbytables I think that the issue that's occurring is that 1P6 is converting the asterisk to the URL encoding (%2A) and that was confusing the lookup. This is what I saw show up in the extension somewhere.

jxpx777

Thanks, @kop48. We'll make sure the Windows team sees this, but I believe once they implement the URL matching that is in place on Mac, it will solve the problem entirely. Stay tuned!

--
Jamie Phelps
Code Wrangler @ AgileBits
Fort Worth, Texas