An option to show full URL without the query string?

[michalrus]

E.g. just https://www.google.com/search for https://www.google.com/search?hl=en&q=blah.

That seems like a useful compromise? =)

[Aternus]

+1

[erichgoldman]

@michalrus Can you tell me more about your use case for this issue? Is this purely cosmetic so you see less? I would expect that the downstream program like KeePass can support a regular expression that just matches like *https://www.google.com/search*.

[DataGhost]

In the example, it could be that some search terms (or other query components) also match another entry in the database, e.g. by title. I've had a specific one when trying to login to Paypa, where "qt" (for qt.io) appeared in the randomised anti-replay string in the query, so that made the entry selection dialog pop up completely unnecessarily.

For me personally, in most cases I'd like to go with the hostname only, including the protocol (so https://host.name/ instead of host.name/). That way I'm also sure the connection is secure. I can see some cases where the path is relevant as well, but I don't know any where the query string is going to be useful so I'd also like to be able to disable that one, just to prevent false positives and possible accidental mis-entry when the user isn't careful.

[erichgoldman]

Hi @DataGhost

also match another entry in the database, e.g. by title.

I would recommend looking to fine tune your auto-type rules with more explicit matches in most cases.

You can also change what fields are used for matching on the auto-type attempt to only use your more custom rules and not other fields in the entry:

where "qt" (for qt.io) appeared in the randomised anti-replay string

For example, in this case it sounds like you have an entry labeled qt in the title field, but if you choose to just match on url and store the full URL like https://qt.io you would get less ambiguous matching

That way I'm also sure the connection is secure.

In most Chrome and FireFox derivatives they should be warning you about insecure connections now. I would also recommend an extension like HTTP Everywhere to address that concern.

If you want to minimize mismatches and overlaps resulting in the selector prompt, I would disable all options URL and then custom auto type rules and then you can use very explicit regex to meet your needs.

[kodfodrasz]

I'm using custom autotype sequences, and used a different plugin earlier, which included the protocol also. I'd prefer not to drop this plugin, as the form field name feature is really useful for new entries going forward, however I'd not edit ~500 autotype sequcences (even though I could script it), but would rather find a checkbox inthe settings to "include prootocol" really handy. I don't see this as a very big feature with big consequences, but can be handy for some people.

Honestly I'm not sure why it needs extra justification. This is a tiny feature which doesn't seem as one that could break anything or have far fetched consequences.