Chrome extension doesn't recognise single-word addresses (on LAN)

Mids

This is probably a minority one, but...
I use 1Password on my local network to log in to my NAS control panel. The address on the local network is in the form of https://nasname:5001/

Using that form of address, which 1Password has in its list of addresses - moved to the top even - it isn't recognized. I have to manually search in the extension for the appropriate login.
It works using https://nasname.local:5001, and by IP address. It seems to simply ignore the one word address.

It doesn't offer to remember a username and password when entered at that address, either.

Chrome is version 59.0.3071.115

---

1Password Version: 6.6.439d
Extension Version: 4.67.90
OS Version: Windows 10 (Build 1703)
Sync Type: Not Provided

littlebobbytables

Hello @Mids,

1Password uses a public suffix list when working with URLs so even before peeking at the code I don't think I'm surprised that it doesn't like those form of addresses. When it looks like xxxx.local the address then has a recognised TLD and a "domain".

Just to make sure I'm not misunderstanding, are you saying autosave doesn't work with https://nasname.local:5001 either but it will if you use the IP address?

Mids

No, it saves fine with https://nasname.local:5001.
The only issue is for nasname without the '.local' suffix.

As I said, a bit of a minority issue.

littlebobbytables

Hi @Mids,

Hopefully using the .local address isn't too much of a pain. I'm not sure where we stand on URLs with no TLD, I'll have to ask.

Mids

As far as inconveniences go, it's pretty minimal. Honestly, the only reason I ran into it at all was that I was setting up self-signed SSL certificates on the NAS, and assigned the certificate to the TLD-free address because it resolves faster on my network than .local addresses do for some reason.

Incidentally, thanks for the quick replies here. :)

AGAlumB

Ah, that makes sense. Likewise, thanks for bringing this up. :)