Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for Keepass2Android URL fields (KP2A_URL_1, ...) #60

Closed
gab opened this issue Aug 18, 2020 · 1 comment
Closed

Add support for Keepass2Android URL fields (KP2A_URL_1, ...) #60

gab opened this issue Aug 18, 2020 · 1 comment

Comments

@gab
Copy link

gab commented Aug 18, 2020

Keepass2Android has supported extra URL fields for from-filling purposes for a long time. It uses the format KP2A_URL_1, KP2A_URL_2 and so forth.

Would it be possible to use those if found, instead of having to create new fields starting with URL to be recognized by keepassnatmsg?

Perhaps you could simply relax the rule of what the URL fields should be named, and accept them if they contain URL in all caps, not just start with it? (Ideally everyone would be a happy family and KP2A, KeePassNatMsg and KeepassXC would agree on a single format, but it sounds hard to achieve.)

You'd have to parse the URL and make sure to ignore those starting with androidapp://, as those are for filling in forms in apps, not web pages. Probably ignoring any URL root that you can't process (do you process anything beyond http:// or https:// ?) is a good idea.

Thank you!

@smorks
Copy link
Owner

smorks commented Sep 2, 2020

this appears to be the same as #57. closing this one.

@smorks smorks closed this as completed Sep 2, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants