Very strict URL recognition.

Giga
Giga
Community Member

I use this very often for the many websites we manage. Therefore i need to login to the backend of CMS's systems.

For example to login the domain is http://www.domain.co.uk/admin/

If i add http://www.domain.co.uk/admin to 1password it doenst find it. Is this logical or is there somehting wrong with the absolute/reltative url recognition? Or is there an option is miss?

Thanks in advance!

Comments

  • svondutch
    svondutch
    1Password Alumni

    Are you adding this a 2nd (or 3d) URL to an existing Login item? If yes, then you need to turn on this setting: File > Preferences (Ctrl+P) > Logins > Lenient URL matching

  • Giga
    Giga
    Community Member
    edited July 2014

    No, i ment the last "/" in the url. It has to be there. I think thats not wanted? I mean, with or without doenst change a thing? Now i have to manually add a "/" to all my logins.

    Nevertheless did this fixed a other issue i encounterd :D Thanks for that! I couldnt figure out why the 2nd and 3th url didnt work:)

  • Hi @Giga,

    That shouldn't matter, it may be the site itself reacting to that "/". Can you tell us where this is happening, so that we can test it? If you want, you can send me a private message here with your URLs.

  • Tiran Kenja
    Tiran Kenja
    Community Member

    I'm seeing something very similar to this - that seems to have happened between the betas and the final version 4 for Windows.

    Lenient URL matching IS on. And yet even a difference in protocol (http vs https) will stop 1Password from matching it.

    As of right now it is with Chrome extension 4.2.3.90 and 1Password for Windows 4.0.0.499

  • svondutch
    svondutch
    1Password Alumni

    a difference in protocol (http vs https) will stop 1Password from matching it.

    This is by design. When you're on a HTTP page and the matching Login item is HTTPS, then 1Password should not fill this Login item.

  • Tiran Kenja
    Tiran Kenja
    Community Member

    I see.

    In any event I also have missing match that is harder to guess the reason for.

    I have a card for my EA login. And among the urls I have is 'https://battlefield.com/' and 'https://store.origin.com/'. The interesting thing is that on 'http://battlelog.battlefield.com/bf4/' it is not matching. But when I go to ea.com and login, it matches 'https://connect.origin.com/dk/ea/login?' (that the login popup uses) fine

  • MikeT
    edited July 2014

    Hi @Tiran Kenja‌,

    That's actually intentional. It is a security risk to fill in a Login that uses https:// protocol on top of insecure http:// site, that's why we made this change to protect you. You have two https:// URLs in your Login item, it will never fill on any http:// page from both URLs until you visit a https:// page.

    If you want 1Password to intentionally fill on http://battelog.battlefield.com/, you must add this manually to the Login item.

  • Tiran Kenja
    Tiran Kenja
    Community Member

    Ah right. It looks like i copied in a http for the battlelog site. Annoyingly browsers tend to hide much of the URL now so I missed that. So it is like the first one I asked about =)

  • :D

    The browser should show the secure lock next to the address bar when its on HTTPS. If not, you may want to install an add-on to show it if possible.

This discussion has been closed.