Website URL schema change in 6.5.x update?
Is it just me, or did the URL schema change for "local" URLs in the 6.5.x update?
Before in the website field, I could have a URL like website:8888 and 1Password could autofill against that. Now it has to be http://website:8888, otherwise autofilling won't work.
It works fine for "normal" URLs like website.com, however. I prefer the shorthand version since I don't like having the http:// in there unless necessary (i.e. if it's a HTTPS URL).
1Password Version: 6.5.1
Extension Version: 4.6.2
OS Version: macOS 10.12.1
Sync Type: 1Password
Comments
-
There were definitely changes made in 6.5 to the detection and parsing of potential URLs. I think most likely what we're seeing here is a failure to match http://website:8888 to what 1Password is doing to "website:8888". We should be able to easily confirm that if you have a site setup that has both http and https and connect to the https version instead. so that https://website:8888 matches against the transformed website:8888 that becomes https://website:8888.
Rudy
0 -
I'm piggybacking on this thread because I am also having issues since the update.
None of my wildcard site entries work any longer: for example https://[*].mydomain.com0 -
Thanks for chiming in, but I think that might've worked by accident rather than intent.
We have a bug OPM-2561 that describes adding wildcard support for login urls that isn't currently implemented. I'll add your request to the list of votes for adding it though.
Rudy
ref: OPM-2561
0 -
seems like that way is a much cleaner and easier to control method than just to just match all against a root domain. It was so much easier to control behavior/logins in that way if you have hundreds logins to manage under subdomains or wanted to include a wildcard url under multiple login items that didn't match the domain...
0 -
seems like that way is a much cleaner and easier to control method than just to just match all against a root domain.
@jr2315323: I think in some cases that may be true, but not everyone knows (or cares) what wildcards are. Perhaps it's a feature we'll be able to add in a future version though for folks like you who will appreciate it. Cheers! :)
0 -
Jeers!
0 -
0
