Autofill behavior when "only fill on this exact domain" is selected (host:port matching)

luckman212
luckman212
Community Member
in 1Password in the Browser

I read the support page Change where a login is suggested and filled and checked around the settings in the app itself. It seems that the undocumented behavior when Only fill on this exact domain is selected is to match on the hostname AND port (if specified).

For example:

If we have an item saved like this (website=https://my-secure-host.com:8080/)

...and you browse to https://my-secure-host.com:8081 then 1P will NOT offer to autofill for that page. This is a good thing in general, but it would be nice if:

  1. This were documented
  2. There was an additional option, to match on exact base URL (ignoring any :port portion)

1Password Version: 8.10.32
Extension Version: 2.23.3
OS Version: macOS 14.5
Browser: Chrome

Comments

  • Dave_1P
    Dave_1P

    Hello @luckman212! 👋

    Thanks for reaching out. The support page that you linked to says the following for the "Only fill on this exact domain" option:

    You’ll see the item as a suggestion only if the domain (hostname and port) is an exact match.

    Let me know if I misunderstood your post. 🙂

    -Dave

  • luckman212
    luckman212
    Community Member

    Hmm yes you're right! I didn't see that yesterday somehow. In any case, suggestion #2 above still stands!

  • EvonG1P
    EvonG1P

    Hello @luckman212, thank you for your reply.

    You mentioned:

    There was an additional option, to match on exact base URL (ignoring any :port portion)

    Can you elaborate on this feature request and share any examples so I can forward them to our product team? Would it be helpful if you added a secondary URL address to your Login item and adjusted the Autofill behaviour for that?

    I look forward to your reply.

    -Evon

  • luckman212
    luckman212
    Community Member

    @EvonG1P Sure! Here's an example:

    Let's say I work for MyCorp. I have a few logins saved in 1Password:

    • foo.mycorp.com
    • buzz.mycorp.com
    • dev.mycorp.com:8081

    ... for each of these I am using the "exact domain" option to prevent them from interfering with each other.

    One day I am browsing our dev server and notice the service has been migrated to another port and now lives on https://dev.mycorp.com:9090.

    It could be useful in this case, if 1P could be configured to automatically suggest the login based on the hostname alone: https://dev.mycorp.com (and yet still exclude foo and buzz)

  • EvonG1P
    EvonG1P

    Hello, @luckman212! Thanks for the additional information. I understand how this can be useful when the ports change on the URL. I've filed a feature request to have the product team look into this.

    Let me know if there's anything else I can assist you with.

    -Evon

    ref: PB-39961231

This discussion has been closed.